operator-controller
operator-controller copied to clipboard
operator-framework
#342 should be followed up with a docs change
**Problem** It is not possible to do rollbacks with OLM currently without workarounds. In case we hit an incident it would help a lot if a customer can easily rollback...
**Problem** For cloud environments we would like to have as much control as we can about the operator installations. We need Operators to be installed declarative, preferably via a simple...
**Problem** Currently we struggle testing the operator with OLM. OLM adds more capabilities, i.e. pre-flight checks, and caused an incident in an ACS release. It is hard to test operator...
**Problem** In ACS we have a clientserver architecture in which our server should always be ahead or equal in its version of the clients. Currently OLM auto-upgrades upgrade upgrade the...
**Problem** The ACS operator runs on over 1,500 clusters, most of them use automatic upgrades. As soon as we publish the ACS operator to the OpenShift catalog all clusters try...
**Problem** For the ACS cloud service we run ACS Central instances bin-packed and want to deploy different versions. Our operator has a 1:1 version mapping which requires running the operator...
We need a check for PRs to make sure that we generate all the generated code and yamls as part of a PR.
I am getting the error `entity for package "registry-operator" not found in solution` when trying to upgrade to next version using skip edges. ## Steps to recreate 1. Use a...
Need to add `cache-dependency-path` configuration option into `setup-go` GitHub action to improve caching. Background: we introduced [bingo](https://github.com/bwplotka/bingo) in OLMv1 repos for managing tools and it created a bunch of modules...