operator-controller
operator-controller copied to clipboard
operator-framework
This issue is to discuss in detail about: - What the `InstalledBundleResource` in `extension.spec` should look like when multiple sources for fetch can be provided. This means a single extension...
This issue is to investigate if the package and channel deprecation statuses can be determined even if the bundle selection after resolution fails. More details: https://github.com/operator-framework/operator-controller/pull/625#discussion_r1508237049
#625 currently supports installation of only plain bundles - where all the manifests are present in a single location. This issue tracks the work required to support registryV1 bundles. The...
Follow up of #625 that adds logic to create App CR from Extension reconciler: - Modify existing test setup in the following locations to include Kapp-controller installation: - e2e test...
In scope: - Registry+v1 bundles only - watchNamespaces - Stretch: `subscription.spec.config`
- This should use the same method as used in OLM v0 (annotation key: 'olm.targetNamespaces')
operator-controller must never use its own permissions to perform actions on behalf of users. Instead, it must use the ServiceAccount listed in the Extension to do so.
Follow up to https://github.com/operator-framework/operator-controller/pull/544. Add example custom resources (CRs)to the version range docs.
