ARO-15578: add disable cluster capabilities flag to cluster create cmd#5775
Conversation
337b3e9 to
b51ab58
Compare
|
/test e2e-aks |
|
/retitle ARO-15578: add disable cluster capabilities flag to cluster create cmd |
|
@flavianmissi: This pull request references ARO-15578 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. 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. |
|
@flavianmissi: This pull request references ARO-15578 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. 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. |
|
@flavianmissi: This pull request references ARO-15578 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. 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. |
1 similar comment
|
@flavianmissi: This pull request references ARO-15578 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. 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. |
|
/retest |
db2f864 to
13ca35b
Compare
98552fc to
13ca35b
Compare
|
Since #5810 has an API change, I'll put this PR on hold until the other lands. I'll remove the hold once I have rebased. |
13ca35b to
bf5b7fd
Compare
4c8c589 to
4208782
Compare
|
rebased with main and updated naming. @jparrill PTAL /hold cancel |
bryan-cox
left a comment
There was a problem hiding this comment.
Other than the minor nit, we should have the why/description in the commit messages per 7. here - https://hypershift.pages.dev/contribute/#prior-to-submitting-a-pull-request.
Not going to hold the PR up for this though.
| flags.StringVar(&opts.ReleaseStream, "release-stream", opts.ReleaseStream, "The OCP release stream for the cluster (e.g. 4-stable-multi), this flag is ignored if release-image is set") | ||
| flags.StringVar(&opts.FeatureSet, "feature-set", opts.FeatureSet, "The predefined feature set to use for the cluster (TechPreviewNoUpgrade or DevPreviewNoUpgrade)") | ||
|
|
||
| flags.StringSliceVar(&opts.DisableClusterCapabilities, "disable-cluster-capabilities", nil, "Optional cluster capabilities to disabled. The only currently supported value is ImageRegistry.") |
There was a problem hiding this comment.
really minor nit
| flags.StringSliceVar(&opts.DisableClusterCapabilities, "disable-cluster-capabilities", nil, "Optional cluster capabilities to disabled. The only currently supported value is ImageRegistry.") | |
| flags.StringSliceVar(&opts.DisableClusterCapabilities, "disable-cluster-capabilities", nil, "Optional cluster capabilities to be disabled. The only currently supported value is ImageRegistry.") |
|
/lgtm |
|
/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main" |
|
@bryan-cox: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. 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 kubernetes-sigs/prow repository. |
|
/override "Red Hat Konflux / hypershift-operator-main-on-pull-request" |
|
@sjenning: Overrode contexts on behalf of sjenning: Red Hat Konflux / hypershift-operator-main-on-pull-request 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 kubernetes-sigs/prow repository. |
|
/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main" |
|
@sjenning: Overrode contexts on behalf of sjenning: Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main 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 kubernetes-sigs/prow repository. |
|
/retest |
|
/hold Revision 5a3fa30 was retested 3 times: holding |
|
test failures look to be flakes. |
|
/hold cancel |
|
@flavianmissi: 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. |
e603b04
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: hypershift |
What this PR does / why we need it:
Which issue(s) this PR fixes
Fixes #ARO-15578
Checklist