Skip to content

Promote RetryGenerateName to GA#127093

Merged
k8s-ci-robot merged 2 commits into
kubernetes:masterfrom
jpbetz:retry-generate-name-ga
Sep 23, 2024
Merged

Promote RetryGenerateName to GA#127093
k8s-ci-robot merged 2 commits into
kubernetes:masterfrom
jpbetz:retry-generate-name-ga

Conversation

@jpbetz

@jpbetz jpbetz commented Sep 3, 2024

Copy link
Copy Markdown
Contributor

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_name metric 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?

Promoted `RetryGenerateName` to stable; the feature is enabled by default. `--feature-gates=RetryGenerateName=true` not needed on kube-apiserver binaries and will be removed in a future release.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 3, 2024
@k8s-ci-robot k8s-ci-robot requested review from dims and tkashem September 3, 2024 14:51
@jpbetz

jpbetz commented Sep 3, 2024

Copy link
Copy Markdown
Contributor Author

/sig api-machinery

@jpbetz

jpbetz commented Sep 3, 2024

Copy link
Copy Markdown
Contributor Author

@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.

@jpbetz

jpbetz commented Sep 3, 2024

Copy link
Copy Markdown
Contributor Author

/assign @deads2k
See description for a question about if we want a metric for this or not.

@Jefftree

Jefftree commented Sep 3, 2024

Copy link
Copy Markdown
Member

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 (

// owner: @jpbetz
// alpha: v1.30
// Resource create requests using generateName are retried automatically by the apiserver
// if the generated name conflicts with an existing resource name, up to a maximum number of 7 retries.
RetryGenerateName featuregate.Feature = "RetryGenerateName"
) is referenced.

Also, 1.32 feature promotion depends on #126977 to land.

@Jefftree

Jefftree commented Sep 3, 2024

Copy link
Copy Markdown
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 3, 2024
@jpbetz jpbetz force-pushed the retry-generate-name-ga branch from f1664b0 to d5db629 Compare September 10, 2024 16:34
@jpbetz

jpbetz commented Sep 10, 2024

Copy link
Copy Markdown
Contributor Author

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

I'm okay with this change, but shouldn't it be applied uniformly to all of apiserver/pkg/kube_features, not piecemeal? Should that be the responsibility of feature owners?

@Jefftree

Copy link
Copy Markdown
Member

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

I'm okay with this change, but shouldn't it be applied uniformly to all of apiserver/pkg/kube_features, not piecemeal? Should that be the responsibility of feature owners?

Most apiserver features are already deduplicated and kube_features imports directly from apiserver/pkg/kube_features. #127186 this PR fixes it for RetryGenerateName

@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 11, 2024
@Jefftree

Copy link
Copy Markdown
Member

@jpbetz CI should work properly after a rebase now that we've bumped compatibility version to 1.32

@jpbetz jpbetz force-pushed the retry-generate-name-ga branch from d5db629 to 4e50d07 Compare September 19, 2024 13:40
@jpbetz

jpbetz commented Sep 19, 2024

Copy link
Copy Markdown
Contributor Author

CI should work properly after a rebase now that we've bumped compatibility version to 1.32

Great, I've rebased.

@jpbetz jpbetz force-pushed the retry-generate-name-ga branch from 4e50d07 to 781e8d3 Compare September 19, 2024 14:45
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 19, 2024
@jpbetz jpbetz force-pushed the retry-generate-name-ga branch 2 times, most recently from 759bc53 to c2dc5d5 Compare September 19, 2024 16:00
Comment thread staging/src/k8s.io/apiserver/pkg/features/kube_features.go
// owner: @jpbetz
// alpha: v1.30
// beta: v1.31
// ga: v1.32

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

yeah I'm +1 on removing these after we have everything ported. We already found quite a few inaccuracies with the comments

Comment thread staging/src/k8s.io/apiserver/pkg/features/kube_features.go
@jpbetz jpbetz force-pushed the retry-generate-name-ga branch from f38f106 to 0d14bac Compare September 19, 2024 18:02

@Jefftree Jefftree left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@Jefftree

Copy link
Copy Markdown
Member

/lgtm
/approve

Feature is targeted for GA in 1.32 kubernetes/enhancements#4420

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 23, 2024
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 7f73e7e9599312435c63113fcfe7dc5442d91dc5

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[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

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

@k8s-triage-robot

Copy link
Copy Markdown

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:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-ci-robot k8s-ci-robot merged commit 1137a6a into kubernetes:master Sep 23, 2024
@k8s-ci-robot k8s-ci-robot added this to the v1.32 milestone Sep 23, 2024
@tengqm

tengqm commented Sep 25, 2024

Copy link
Copy Markdown
Contributor

Please propose a PR to the website for this promotion.

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. area/apiserver cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants