-
Notifications
You must be signed in to change notification settings - Fork 585
config/v1/types_cluster_version: Add insights #1212
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
Conversation
|
Hello @rluders! Some important instructions when contributing to openshift/api: For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard
OR
Who should apply these qe/docs/px labels?
|
|
Do you have the other PRs created that tag these resources appropriately? Can you link them here? If they haven't already merged, it would be best to merge them first so that once this merges and gets vendored, the new capabilities values can be used successfully. |
@bparees do you mean this one? openshift/insights-operator#646 |
yes, thanks. fyi we've created some guidance for how to order the PRs related to capabilities changes: (my suggestion to merge your resource annotation PR first was actually incorrect because the CVO will start excluding those resources immediately if you did so. The new cap name has to be defined+vendored into the CVO repo first) |
|
/test verify |
|
Who is supposed to provide no-FF labels here please? Insighs QE & docs or some other team? |
|
failing on a diff between what you are providing and the generated crd yaml: do a |
|
(and make sure you're rebased on latest master first) |
Turns out anyone can do that. Although with out renewed focus on shipping features sprintly, it may be best to try to loop in the relevant teams for each label, just so they're all aware and lined up ready to doc/QE/etc. the new feature as the pull requests following this one bring it into 4.12 nightlies. |
|
Opened a docs issue in CCXDEV: https://issues.redhat.com/browse/CCXDEV-8766 /label docs-approved |
|
/label qe-approved |
config/v1/types_cluster_version.go
Outdated
|
|
||
| // ClusterVersionCapability enumerates optional, core cluster components. | ||
| // +kubebuilder:validation:Enum=openshift-samples;baremetal;marketplace | ||
| // +kubebuilder:validation:Enum=openshift-samples;baremetal;marketplace;insights |
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.
@deads2k When an enum like this is using the wrong casing, what are your thoughts on updating it to allow these existing values but making new values PascalCase to fit the expected Kube conventions?
Something like this maybe with a developer note as to why some are duplicated. Consumers would have to be updated to observe both old and new values
| // +kubebuilder:validation:Enum=openshift-samples;baremetal;marketplace;insights | |
| // --- | |
| // + Old lowercase values left for compatibility, new values should be added as PascalCase | |
| // +kubebuilder:validation:Enum=OpenShiftSamples;Baremetal;MarketPlace;Insights;openshift-samples;baremetal;marketplace |
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.
The sins of the past. I am in favor of addressing this and the proposed solution is reasonable, but it will require a backport and an explanation (probably better a PR) of how to the CVO will handle it and backport. I'd like to work out and merge the CVO handling before adding the toleration here.
If @wking is amenable to making the CVO ToLower the value, then merging this one as "Insights" makes sense. If he's not, then I would release this one as "insights" and try to convince him before making the change.
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.
Renamed it to Insights
|
/approve |
Add insights operator as a capability config/v1/types_cluster_version: version cap 4.12 - Adds the version capability set 4.12 - Moves insights cabability to version 4.12 config/v1/types_cluster_version: adds insights cap to current add capability set to cvo config crd update cvo cr manifest rename insights to Insights
|
@rluders: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
|
Is this connected to https://issues.redhat.com/browse/CCXDEV-8079? |
|
/label px-approved |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, JoelSpeed, rluders 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 |
Add insights operator as a capability.