-
Notifications
You must be signed in to change notification settings - Fork 1.5k
OPRUN-3588: Add OperatorLifecycleManagerV1 capability #9196
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
OPRUN-3588: Add OperatorLifecycleManagerV1 capability #9196
Conversation
to pull in the changes that add the OperatorLifecycleManagerV1 capability to these libraries. Signed-off-by: everettraven <[email protected]>
|
/hold |
|
/retest |
1 similar comment
|
/retest |
tmshort
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
Add OPRUN-3588: to the PR title =D |
|
@everettraven: This pull request references OPRUN-3588 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@installer-team Can you please take a look. We need this PR before code branch for 4.18 happens. |
|
@everettraven: This pull request references OPRUN-3588 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
openshift/cluster-version-operator#1108 is the PR to add the capability to CVO |
|
@everettraven: This pull request references OPRUN-3588 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@everettraven the install config crd can be generated with Can you squash the fix commit? It looks like this pr is just vendoring new dependencies and then generating the new crd, so if you want to squash everything into one commit that is fine too |
as a new allowed enum value for the additionalEnabledCapabilities Signed-off-by: everettraven <[email protected]>
c4c7b82 to
2abc622
Compare
|
@patrickdillon I rolled the fix commit into the commit to regenerate the CRD |
|
/approve |
|
/hold cancel |
|
/lgtm |
LalatenduMohanty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LalatenduMohanty, patrickdillon, tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@everettraven: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Updates the
InstallConfig.capabilities.additionalEnabledCapabilitiesto add theOperatorLifecycleManagerV1capability.Updated openshift/api, openshift/library-go, openshift/client-go to the latest versions to pull in the new capability
Prior ART for adding CVO capability: