GitHub / operator-framework/operator-controller issues and pull requests
Labelled with: olm-v1/m3
#170 - Operator-Controller resolution considers spec.channel
Issue -
State: closed - Opened by awgreene over 2 years ago
Labels: olm-v1/m3
#169 - Introduce spec.channel field to the operator API
Issue -
State: closed - Opened by awgreene over 2 years ago
Labels: olm-v1/m3
#167 - Handling multiple controller-side validations
Issue -
State: open - Opened by perdasilva over 2 years ago
Labels: kind/design, priority/important-soon, olm-v1/m3
#163 - Honoring an optional `spec.channel` field in the `Operator` API.
Issue -
State: closed - Opened by joelanford over 2 years ago
- 4 comments
Labels: olm-v1/m3
#162 - Honoring an optional `spec.version` field in the `Operator` API
Issue -
State: closed - Opened by joelanford over 2 years ago
- 7 comments
Labels: olm-v1/m3
#161 - Use a catalogd-defined catalog to install an Operator
Issue -
State: closed - Opened by joelanford over 2 years ago
- 1 comment
Labels: olm-v1/m3
#142 - Add .spec.version
Pull Request -
State: closed - Opened by perdasilva over 2 years ago
- 7 comments
Labels: olm-v1/m3
#141 - DNR: Wip: Poc/catsrc v2
Pull Request -
State: closed - Opened by varshaprasad96 over 2 years ago
- 7 comments
Labels: needs-rebase, do-not-merge/work-in-progress, olm-v1/m3