Skip to content

fix(operatorgroups): write out CSV status on OperatorGroup issues #669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

njhale
Copy link
Member

@njhale njhale commented Jan 15, 2019

  • Adds 3 new CSV transition reasons: NoOperatorGroup, TooManyOperatorGroups, and UnsupportedOperatorGroup
  • Transitions CSVs to failed with the approriate status reason whenever an OperatorGroup issue is detected
  • OperatorGroup reconciliation annotates CSVs in any phase
  • Update InstallModes supports logic

Addresses ALM-862 and ALM-853

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jan 15, 2019
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2019
@@ -236,6 +236,13 @@ The metadata section contains general metadata around the name, version and othe

**Selectors** (optional): A label selector to identify related resources. Set this to select on current labels applied to this CSV object (if applicable).

**InstallModes**: A set of `InstallMode`s that tell OLM which `OperatorGroup`s an Operator can belong to. An `InstallMode` consists of an `InstallModeType` and a boolean `Supported` flag. There are four `InstallModeTypes`:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should mention the specific way that an operator "supports" an InstallMode - which is that it understands the OLM-written annotations on the pods

@njhale njhale force-pushed the csv-installmode-status branch from f453526 to 9ce8acb Compare January 15, 2019 17:19
- Adds 3 new CSV transition reasons: NoOperatorGroup, TooManyOperatorGroups, and UnsupportedOperatorGroup
- Transitions CSVs to failed with the approriate status reason whenever an OperatorGroup issue is detected
- OperatorGroup reconciliation annotates CSVs in any phase
- Update InstallModes supports logic
@njhale njhale force-pushed the csv-installmode-status branch from 9ce8acb to efb2a2a Compare January 15, 2019 17:39
@ecordell
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2019
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ecordell, njhale

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit f633e44 into operator-framework:master Jan 15, 2019
ecordell pushed a commit to ecordell/operator-lifecycle-manager that referenced this pull request Mar 8, 2019
…-status

fix(operatorgroups): write out CSV status on OperatorGroup issues
@njhale njhale added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 19, 2019
@njhale njhale deleted the csv-installmode-status branch September 30, 2019 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants