Promote RetryGenerateName to GA#127093
Conversation
|
/sig api-machinery |
|
@aaron-prindle Just a heads up that this might collide with your feature migration. I'm happy to merge after your PR and re-base. |
|
/assign @deads2k |
|
Ah this is one of the more involved features to port that involves a definition both in kube_features and apiserver/pkg/kube_features. I think we should consolidate the names so only one variable ( kubernetes/staging/src/k8s.io/apiserver/pkg/features/kube_features.go Lines 203 to 207 in f1664b0 Also, 1.32 feature promotion depends on #126977 to land. |
|
/triage accepted |
f1664b0 to
d5db629
Compare
I'm okay with this change, but shouldn't it be applied uniformly to all of |
Most apiserver features are already deduplicated and |
|
@jpbetz CI should work properly after a rebase now that we've bumped compatibility version to 1.32 |
d5db629 to
4e50d07
Compare
Great, I've rebased. |
4e50d07 to
781e8d3
Compare
759bc53 to
c2dc5d5
Compare
| // owner: @jpbetz | ||
| // alpha: v1.30 | ||
| // beta: v1.31 | ||
| // ga: v1.32 |
There was a problem hiding this comment.
nit: These stability level comments feel unnecessary for versioned feature gates. Worse, there is a risk that these comments will fall out of sync with the versioned feature gate information. We might consider removing these once fully migrated.
There was a problem hiding this comment.
yeah I'm +1 on removing these after we have everything ported. We already found quite a few inaccuracies with the comments
f38f106 to
0d14bac
Compare
|
/lgtm Feature is targeted for GA in 1.32 kubernetes/enhancements#4420 |
|
LGTM label has been added. DetailsGit tree hash: 7f73e7e9599312435c63113fcfe7dc5442d91dc5 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Jefftree, jpbetz 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 |
|
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
|
Please propose a PR to the website for this promotion. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Special notes for your reviewer:
Do we want the
retry_for_generate_namemetric originally proposed for GA? Looking at the adjacent labels for request metrics ("verb", "dry_run", "group", "version", "resource", "subresource", "scope", "component", "code"), this feels somewhat out-of-place..Does this PR introduce a user-facing change?