operator-registry
operator-registry copied to clipboard
operator-framework
Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.
**Description of the change:** Replaces #1814 Various type changes and refactoring necessary to make opm alpha render-template capable of detecting the template type from sniffing its schema, as well as...
**Description of the change:** Adds a new bundle-scoped "release" flag to the existing version property to allow for more sophisticated replacement strategies with improved transparency. Adds a new substitutesFor catalog...
**Description of the change:** When verifying channel validity, halt replaces chain traversal when we encounter a bundle that is skipped by any other entry anywhere in the channel. **Motivation for...
… **Description of the change:** **Motivation for the change:** **Reviewer Checklist** - [ ] Implementation matches the proposed design, or proposal is updated to match implementation - [ ] Sufficient...
**Description of the change:** Update the go directive in go.mod from 1.24.6 to 1.24.10 to solve multiple issues described in https://github.com/operator-framework/operator-registry/issues/1841. **Motivation for the change:** Internal security scanners flagged this...
Signed-off-by: Joe Lanford WIP: This is an implementation with few tests. Before merge, we need to add some tests to ensure migrations work as expected and GRPC compatibility is maintained....
Our security scanners are flagging the current opm image because it is built with a vulnerable Go version. The following Go-related CVEs are being reported: CVE-2025-47912, CVE-2025-58183, CVE-2025-58185, CVE-2025-58186, CVE-2025-58188,...
Currently, you manually have to add the icon to the generated `olm.package`. It would be nice if this can be added to the template, or is otherwise picked up from...
Some breaking changes were introduced in opm v1.53.0 which prevent us from using envvar `REGISTRY_AUTH_FILE` and we get `unauthorized` error. Note that it works well with opm v1.52.0
It seems like `opm` fails to authenticate with a private registry when it encounters a Docker config such as this one: ``` { "credsStore": "osxkeychain" } ``` So this prevents...
Metadata
Owner
Metadata
Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.