-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EndpointSlice API GA Doc Updates for 1.21 #27070
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 02afb71 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/605bb3a821e6be0008e4e59a |
/cc @robscott |
Thanks for the work on this! I think you'll also need changes to a couple more files: |
/sig network |
thank you for opening this! /assign |
a2667e6
to
723bff2
Compare
723bff2
to
2482dec
Compare
2482dec
to
6d98cb5
Compare
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
7162b14
to
0aeb542
Compare
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
be supported in the v1 API. Instead, the v1 API supports setting individual | ||
node name and zone fields. These fields will be automatically translated | ||
between API versions. For example, the value of | ||
topology[topology.kubernetes.io/zone] in the v1beta1 API will be accessible in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
topology[topology.kubernetes.io/zone] in the v1beta1 API will be accessible in | |
`topology.kubernetes.io/zone` in the v1beta1 API are available as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The field in the API is topology
which is a map. In this case we are referring to the key value pair topology[topology.kubernetes.io/zone]
. I added backticks, does that make it clearer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe topology["topology.kubernetes.io/zone"]
would be slightly clearer? Agree that the topology[
prefix adds important context here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Since topology
is a map, and topology.kubernetes.io/zone
is a key in that map, we may want to revise the sentence so that the text is more clearer for YAML developers/users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have called out that topology.kubernetes.io/zone
as a key in the topology
field in the new version. Let me know if the text is clear enough now. I am not exactly sure how to describe it for YAML users.
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/services-networking/endpoint-slices.md
Outdated
Show resolved
Hide resolved
bc0cda7
to
c654dfb
Compare
Because of kubernetes/kubernetes#100472, I have added doc changes to mention the deprecation. |
c654dfb
to
d6ec436
Compare
d6ec436
to
b503fb8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit more feedback. We can merge this as-is; however there are a couple of points about factual accuracy that we might want to look at.
content/en/docs/tasks/administer-cluster/enabling-endpointslices.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/enabling-endpointslices.md
Outdated
Show resolved
Hide resolved
4c7471a
to
c165a73
Compare
Newest update removes Thanks for all the feedback! |
* Deprecate `endpointslices.discovery.k8s.io/v1beta1` * Removes `content/en/docs/tasks/administer-cluster/enabling-endpointslices.md` and redirects requests to that page to `content/en/docs/concepts/services-networking/endpoint-slices.md`
c165a73
to
02afb71
Compare
/lgtm |
LGTM label has been added. Git tree hash: f8ec686c90f0e1e6c2356a6261eba66401b1722c
|
@reylejano this seems to have all the concerns addressed, is it ok to approve? |
Several sig doc members have made reviews and theirs comments have been addressed @robscott can you give a technical lgtm |
@kubernetes/sig-network-pr-reviews please provide a tech review for this PR by 31st of March in order to get it into the release. |
Thanks! /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: reylejano The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR includes the doc updates required since EndpointSlice is going GA in 1.21.