Closed gregsheremeta closed 3 years ago
Hi @gregsheremeta. Thanks for your PR.
I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Kubernetes community operators were moved to https://github.com/k8s-operatorhub/community-operators/tree/main/operators. Please make PR there. Thanks for understanding.
Signed-off-by: Greg Sheremeta gshereme@redhat.com
Updates to existing Operators
ci.yaml
file according to the update instructions?replaces
property if you chosereplaces-mode
via theupdateGraph
property inci.yaml
?package.yaml
orannotations.yaml
?Your submission should not
upstream-community-operators
andcommunity-operators
at onceOperator Description must contain (in order)
Operator Metadata should contain