Skip to content

Conversation

@raspbeep
Copy link
Contributor

@raspbeep raspbeep commented Jul 21, 2022

Introduces the console as a new capability and adds new versioned capability set for the current version of OCP.

https://issues.redhat.com/browse/CONSOLE-3221

Link to PR introducing to console-operator manifests: openshift/console-operator#665

Pavel Kratochvil added 2 commits July 21, 2022 12:15
Signed-off-by: Pavel Kratochvil <[email protected]>
@openshift-ci openshift-ci bot requested review from eparis and sttts July 21, 2022 10:35
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 21, 2022

Hello @raspbeep! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard lgtm and approved labels this repository requires either:

bugzilla/valid-bug - applied if your PR references a valid bugzilla bug

OR

qe-approved, docs-approved, and px-approved - these labels can be applied by anyone in the openshift org via the /label command.

Who should apply these qe/docs/px labels?

  • For a no-Feature-Freeze team who is merging a feature before code freeze, they need to get those labels applied to their api repo PR by the appropriate teams (i.e. qe, docs, px)
  • For a Feature Freeze (traditional) team who is merging a feature before FF, they can self-apply the labels (via /label commands), they are basically irrelevant for those teams
  • For a Feature Freeze team who is merging a feature after FF, the PR should be rejected barring an exception

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 21, 2022

Hi @raspbeep. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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 kubernetes/test-infra repository.

@raspbeep
Copy link
Contributor Author

Hi @sttts @eparis, could you review this one please?

Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

/lgtm
/hold

Could you create a PR for adding the annotation to the console-operator repo?

@bparees to confirm our actions. We need:

  1. merge api change (this) PR
  2. vendor the api change into the cvo repo
  3. merge change that introduces new annotation in the console-operator
  4. vendor api changes into the installer repo

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 25, 2022
@jhadvig
Copy link
Member

jhadvig commented Jul 25, 2022

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 25, 2022
@jhadvig
Copy link
Member

jhadvig commented Jul 25, 2022

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 25, 2022
@bparees
Copy link
Contributor

bparees commented Jul 25, 2022

Signed-off-by: Pavel Kratochvil <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 26, 2022
@jhadvig
Copy link
Member

jhadvig commented Jul 27, 2022

QE Approver:

/assign @yapei
Docs Approver:

/assign @opayne1
PX Approver:
/assign @RickJWagner

@jhadvig
Copy link
Member

jhadvig commented Jul 27, 2022

/retitle CONSOLE-3221: Add console capability

@openshift-ci openshift-ci bot changed the title Add console capability CONSOLE-3221: Add console capability Jul 27, 2022
@opayne1
Copy link

opayne1 commented Jul 27, 2022

/label docs-approved

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Jul 27, 2022
@RickJWagner
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Jul 27, 2022
@yanpzhan
Copy link

@raspbeep @jhadvig Hi, could you pls tell me for QE how to test this pr?

@jhadvig
Copy link
Member

jhadvig commented Jul 29, 2022

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jul 29, 2022
@yanpzhan
Copy link

yanpzhan commented Aug 1, 2022

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 1, 2022
@yanpzhan
Copy link

yanpzhan commented Aug 1, 2022

Since we could not test console capability feature against this pr directly, will test the feature after this pr/related pr merged.

@jhadvig
Copy link
Member

jhadvig commented Aug 1, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 1, 2022
@raspbeep
Copy link
Contributor Author

raspbeep commented Aug 1, 2022

/assign @soltysh
We need to merge this API change first to be able to test this PR.

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, raspbeep, soltysh

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

The pull request process is described here

Details 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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 1, 2022
@jhadvig
Copy link
Member

jhadvig commented Aug 1, 2022

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2022

@raspbeep: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 9db3a0c into openshift:master Aug 1, 2022
wking added a commit to wking/openshift-api that referenced this pull request Aug 1, 2022
The lowercase form just landed via 9db3a0c (CONSOLE-3221: Add
console capability (openshift#1232), 2022-08-01), and that matched the
lower-case precedent which we had been using for these enumerated
capabilities.  But the Kube-API preference is for PascalCase [1], so
this commit pivots to that form.  Because we are so close on the heels
of the original change, we don't need to preserve any references to
the outgoing form.  Adjusting the 4.11 references like
openshift-samples will take more dancing, and can happen in follow-up
work.

Generated with:

  $ sed -i 's|\(capability[.]openshift[.]io/name\): console|\1: Console|' $(git grep -l 'capability.openshift.io/name: console')
  $ sed -i 's/console/Console/' config/v1/*version*

And then backing out one godocs hit that the above made:

  $ sed -i 's/the web Console/the web console/' config/v1/*version*

[1]: https://github.com/openshift/enhancements/blame/b3f5408be4505e37c0bdb7f8b2630a92a5d01457/dev-guide/api-conventions.md#L195
SzucsAti pushed a commit to SzucsAti/api that referenced this pull request Aug 15, 2022
* Add console capability

Signed-off-by: Pavel Kratochvil <[email protected]>

* Add version entry for v4.12 and its capabilities

Signed-off-by: Pavel Kratochvil <[email protected]>

* make verify

Signed-off-by: Pavel Kratochvil <[email protected]>

* Add console capability annotation to CRDs

Signed-off-by: Pavel Kratochvil <[email protected]>

Co-authored-by: Pavel Kratochvil <[email protected]>
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. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants