operator-controller
operator-controller copied to clipboard
Follow up to https://github.com/operator-framework/operator-controller/pull/544. Create docs that describe: - `spec.version` field in general - resolution (briefly, then link out to expanded doc on dependency resolution) - Unspecified version - Specified...
Follow up to #544. Include information on [working with pre-release versions](https://github.com/Masterminds/semver/blob/2f39fdc11c33c38e8b8b15b1f04334ba84e751f2/README.md#working-with-prerelease-versions) and `semver` in general.
**Problem** As a user I want to be able to adjust resources installed by an operator with the same flexibility as Helm or manifests provide. The problem faced is that...
From: https://github.com/operator-framework/operator-controller/pull/541#discussion_r1397450515 > If you follow [this code](https://github.com/operator-framework/operator-lifecycle-manager/blob/7d4f29f923579a3b2363dd031c724139b88b8100/pkg/controller/operators/catalog/operator.go#L2086) you can see how to generate a validator for a structural schema. Then you can run this a couple orders of magnitude...
If an operator performs certain actions when upgrading to the next minor version, such as database schema migrations, we should find a way for the operator author to indicate "when...
As part of https://github.com/operator-framework/operator-controller/pull/533 we highlight the new `spec.upgradeConstraintPolicy` behavior and how when it is set to `Enforce` semver is followed and upgrades across a major version are not able...
**Steps to reproduce:** 1. Create a catalog on cluster: `kubectl apply -f config/samples/catalogd_operatorcatalog.yaml` 1. Create a `BundleDeployment`: ```yaml apiVersion: core.rukpak.io/v1alpha1 kind: BundleDeployment metadata: name: operator-sample-manual spec: provisionerClassName: core-rukpak-io-plain template: metadata:...
Once #520 get merged we want to update cache settings (and BD labelling, if necessary) to filter BDs by some label selector so that we're not caching _all_ BDs in...
During the Open Steering Committee meeting on Wednesday November 1st we discussed ways to better share our successes with the community and how this can be time consuming. As a...
As reported in https://github.com/operator-framework/operator-controller/issues/481#issuecomment-1777224014 it seems like extension-developer-e2e job occassionally reports green when it should be be reporting red. This allowed #444 to be merged without updating test data.