Skip to content

KEP-1880 - #46947

Merged
k8s-ci-robot merged 1 commit into
kubernetes:dev-1.31from
aojea:kep1880
Jul 25, 2024
Merged

KEP-1880#46947
k8s-ci-robot merged 1 commit into
kubernetes:dev-1.31from
aojea:kep1880

Conversation

@aojea

@aojea aojea commented Jun 24, 2024

Copy link
Copy Markdown
Member

KEP kubernetes/enhancements#1880

Moves to beta disabled by default in 1.31

@k8s-ci-robot k8s-ci-robot added this to the 1.31 milestone Jun 24, 2024
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 24, 2024
@aojea
aojea marked this pull request as draft June 24, 2024 09:55
@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jun 24, 2024
@netlify

netlify Bot commented Jun 24, 2024

Copy link
Copy Markdown

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name Link
🔨 Latest commit 9c209a8
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/669767e01fddf400084d37d3

@netlify

netlify Bot commented Jun 24, 2024

Copy link
Copy Markdown

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 9c209a8
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/669767e084b1750008dbe1aa
😎 Deploy Preview https://deploy-preview-46947--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@sftim

sftim commented Jun 24, 2024

Copy link
Copy Markdown
Contributor

/sig network

per https://kep.k8s.io/1880

@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Jun 24, 2024
@Princesso

Copy link
Copy Markdown
Contributor

Hello @aojea 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday July 16th 2024 18:00 PST. Thank you!

@Princesso

Copy link
Copy Markdown
Contributor

Hi @aojea, a gentle reminder that tomorrow is the deadline for having your Docs PR ready for review. Please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before tomorrow, Tuesday, July 16th, 2024 18:00 PST.

@aojea aojea changed the title Placeholder PR for KEP-1880 KEP-1880 Jul 15, 2024
@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jul 15, 2024
@aojea
aojea marked this pull request as ready for review July 15, 2024 08:37
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 15, 2024
@k8s-ci-robot
k8s-ci-robot requested review from sftim and windsonsea July 15, 2024 08:37
@aojea

aojea commented Jul 15, 2024

Copy link
Copy Markdown
Member Author

@Princesso updated to reflect the feature gate state, the rest of functionality is already documented

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

@aojea We should also update the feature state in the reference page (here) to accurately reflect its in beta after promotion in v1.31.

Consider using the suggestion below when updating the feature state (here); it’s a data-driven method that will pull data from the feature gate description file, saving us the need for manual updates in the future.

- {{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+ {{< feature-state feature_gate_name="MultiCIDRServiceAllocator" >}}

Where to change: /docs/reference/networking/virtual-ips.md

Signed-off-by: Antonio Ojea <aojea@google.com>
@aojea

aojea commented Jul 17, 2024

Copy link
Copy Markdown
Member Author

changes applied @dipesh-rawat

fromVersion: "1.27"
toVersion: "1.30"
- stage: beta
defaultValue: false

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This feature is promoted to Beta and its default remains "false"?
Why the promotion then?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Since https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/3136-beta-apis-off-by-default the betas APIs are off by default, this present a challenge for new features that depend on new APIS.

It depends on each feature you can choose to be feature-gate and API beta both to be on or off by default, but not independently, in this case we apply https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/3136-beta-apis-off-by-default and we switch the API off , hence the feature has to be off or it will fail to run.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hello @aojea 👋! v1.31 Doc Lead here. Just checking in as we approach Docs Freeze on Tuesday July 30th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze. Thank you!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

this is just updating a feature gate, so no much technical to review

@danwinship @thockin can you PTAL and LGTM if you are ook with it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@aojea Thanks for the explanation. So the "root cause" is that beta APIs are not enabled by default, just as alpha APIs... sigh.

/approve

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

nope, sorry, is not about enabling, is about being served byt the apiserver, alpha and beta APIs are not served by default , you need to enable them in the apiserver with the -runtime-config flag.

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2024
@windsonsea

Copy link
Copy Markdown
Member

/lgtm

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

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 7caa461ff99f74d20cb066ddadd8de5ea0b5e174

@k8s-ci-robot
k8s-ci-robot merged commit e295a65 into kubernetes:dev-1.31 Jul 25, 2024
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/network Categorizes an issue or PR as relevant to SIG Network. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants