An Operator targeting OpenShift / OKD
Issues/Proposals regarding Best Practices for well-designed/well-behaved Operators
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Higher priority than priority/awaiting-more-evidence.
Highest priority. Must be actively worked on as someone's top priority right now.
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Denotes a PR that changes 100-499 lines, ignoring generated files.
Denotes a PR that changes 30-99 lines, ignoring generated files.
Denotes a PR that changes 10-29 lines, ignoring generated files.
Denotes a PR that changes 500-999 lines, ignoring generated files.
Denotes a PR that changes 0-9 lines, ignoring generated files.
Denotes a PR that changes 1000+ lines, ignoring generated files.
Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).
Force to run deploy on k8s for all cases.
Manually tested and verified to work on a vanilla Kubernetes cluster
Manually tested and verified to work on an OpenShift cluster
Denotes an issue that blocks the tide merge queue for a branch while it is open.
Denotes a PR that should use a standard merge by tide when it merges.
Denotes a PR that should be rebased by tide when it merges.
Denotes a PR that should be squashed by tide when it merges.
Indicates an issue is a duplicate of other open issue.
Indicates an issue needs more information in order to work on it.