featuregate for catalogd metas web api#2202
featuregate for catalogd metas web api#2202openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
Conversation
|
Hello @grokspawn! Some important instructions when contributing to openshift/api: |
47b1d07 to
9628bae
Compare
| contactPerson("jordank"). | ||
| productScope(ocpSpecific). | ||
| enhancementPR("https://github.com/openshift/enhancements/pull/1749"). | ||
| enableForClusterProfile(SelfManaged, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). |
There was a problem hiding this comment.
This is deliberately not being enabled for HyperShift clusters?
There was a problem hiding this comment.
No, I think this is just where I'm uncertain about how to go about this. There are Hypershift and SelfManaged options, and I need the latter, but it's unclear how to also enable the former.
Do I list the feature twice (once for each)? Is Hypershift a superset of SelfManaged?
Without some feedback from SNO reviewers I don't think we want this landing as a surprise there, but otherwise this feature should be everywhere else.
There was a problem hiding this comment.
Ooh. Having played with it a bit, it appears that Hypershift is a superset of SelfManaged, so I /think/ I've fixed it.
There was a problem hiding this comment.
NewOLM is not enabled on Hypershift (yet), therefore any new subfeature of NewOLM (like this one) should also not be enabled on hypershift.
9628bae to
de712d2
Compare
de712d2 to
5c3885a
Compare
|
Didn't see anything in the CI failures that looked actionable, and was able to bring up a cluster with this PR merged, so I'm calling this 'infra' and re-kicking. /retest |
features/features.go
Outdated
| enableForClusterProfile(SelfManaged, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade, configv1.Default). | ||
| mustRegister() | ||
|
|
||
| FeatureGateNewOLMCatalogdMetas = newFeatureGate("NewOLMCatalogdMetas"). |
There was a problem hiding this comment.
Should we include APIV1 in the name in case there is ever an /api/v2/metas endpoint behind a different feature gate?
| FeatureGateNewOLMCatalogdMetas = newFeatureGate("NewOLMCatalogdMetas"). | |
| FeatureGateNewOLMCatalogdMetas = newFeatureGate("NewOLMCatalogdAPIV1Metas"). |
features/features.go
Outdated
| contactPerson("jordank"). | ||
| productScope(ocpSpecific). | ||
| enhancementPR("https://github.com/openshift/enhancements/pull/1749"). | ||
| enableForClusterProfile(Hypershift, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). |
There was a problem hiding this comment.
As I mentioned in another thread, NewOLM (the parent feature for OLMv1) is not yet enabled in Hypershift. This feature gate needs to align with NewOLM.
| enableForClusterProfile(Hypershift, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). | |
| enableForClusterProfile(SelfManaged, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). |
| contactPerson("jordank"). | ||
| productScope(ocpSpecific). | ||
| enhancementPR("https://github.com/openshift/enhancements/pull/1749"). | ||
| enableForClusterProfile(SelfManaged, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). |
There was a problem hiding this comment.
I think you just want to enable everywhere and not make a distinction between cluster profiles
| enableForClusterProfile(SelfManaged, configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). | |
| enableIn(configv1.DevPreviewNoUpgrade, configv1.TechPreviewNoUpgrade). |
There was a problem hiding this comment.
That would enable us for hypershift, and the new feature flag can't be enable there because its "parent" NewOLM cannot be enabled there yet.
There was a problem hiding this comment.
Ack, in which case you have it correct already!
|
/approve Will let @joelanford add the LGTM if he is happy with the name |
Signed-off-by: Jordan Keister <jordan@nimblewidget.com>
Signed-off-by: Jordan Keister <jordan@nimblewidget.com>
9b88560 to
cedb085
Compare
|
/lgtm Thanks for the review @JoelSpeed ! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: grokspawn, joelanford, JoelSpeed 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 |
|
/retest-required |
|
@grokspawn: 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-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
No description provided.