-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
kep-1965: update doc references for APIServerIdentity #37921
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
I recommend adding a short, simple page inside https://kubernetes.io/docs/concepts/overview/working-with-objects/: In that page, outline what a Lease is and where Kubernetes uses them. |
I agree this would be useful, but admittedly also going outside the scope of this KEP to write general documentation about Leases. I will try to find the time to work on this but no promises :) |
Second-mover disadvantage: the SIG that makes the general API gets to write up specific, whereas making good use of the existing API means the new documentation only makes sense following a tidying and reorganization. For GA, we'll want the docs about API server identity leases to have a home somewhere (and not just in the list of former feature gates). Optional but also recommened: revise pages within https://kubernetes.io/docs/tasks/debug/debug-cluster/ |
I think general documentation about Leases and their uses (kube-apiserver identtiy being one of many) would be good to have, and I am happy to try to work on it during regular development cycle. I just don't have time to work on this right now. |
Hi @andrewsykim! This PR needs a doc review by Mon Nov 28th to get this into the release. Please reach out to required SIGs to get their review. Thank you! |
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.
As well as documenting the feature gate, please document how Kubernetes behaves when this is enabled. A few lines may be enough; zero documentation is not sufficient.
See #37921 (comment)
@@ -62,7 +62,8 @@ For a reference to old feature gates that are removed, please refer to | |||
| `APIPriorityAndFairness` | `true` | Beta | 1.20 | | | |||
| `APIResponseCompression` | `false` | Alpha | 1.7 | 1.15 | | |||
| `APIResponseCompression` | `true` | Beta | 1.16 | | | |||
| `APIServerIdentity` | `false` | Alpha | 1.20 | | | |||
| `APIServerIdentity` | `false` | Alpha | 1.20 | 1.26 | |
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.
| `APIServerIdentity` | `false` | Alpha | 1.20 | 1.26 | | |
| `APIServerIdentity` | `false` | Alpha | 1.20 | 1.25 | |
x posting my slack comment I agree, the PR does not add sufficient documentation just yet. About the PR comment:
Seems to me like a bit like an ownership issue, who “bootstraps general docs”. Perhaps we have missed to introduce the documentation page a while back? |
@andrewsykim if you write the text for the |
/assign @enj |
ack, will add this later today |
21b0c0a
to
b2cb7ee
Compare
Signed-off-by: Andrew Sy Kim <[email protected]>
b2cb7ee
to
26d8ad4
Compare
Signed-off-by: Andrew Sy Kim <[email protected]>
68f5b10
to
991a4a3
Compare
I added some general docs for Leases, PTAL. Docs definitely can use more details, but trying to be mindful of the docs deadline today. Definitely needs to be a follow-up to add more content in this area. |
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.
LGTM for docs
I don't think this needs tech review; I can see that these pages look right enough.
/lgtm
/approve
HA configurations, where only one instance of the component should be actively running while the other | ||
instances are on stand-by. | ||
|
||
## kube-apiserver identity |
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.
## kube-apiserver identity | |
## API Server identity |
LGTM label has been added. Git tree hash: 73b37c1dbd940030dd9a766297af49747b756ba4
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
After the release, we can track an issue to mention that workloads / out-of-tree things are also welcome to use Leases (especially controllers and operators). |
|
||
{{< feature-state for_k8s_version="v1.26" state="beta" >}} | ||
|
||
Starting in Kubernetes v1.26, each `kube-apiserver` uses the Lease API to publish its identity to the |
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.
Should we provide more details on the specifics here? Like if I want to build an external integration that uses this information, how would I know what to look for?
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.
More detail is good. IMO we don't need that for beta.
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.
Added more details in #38196
Signed-off-by: Andrew Sy Kim [email protected]
Update feature gate reference for APIServerIdentity. Currently on the fence about whether we want more comprehensive documentation for this feature. In it's current state it is mainly going to be used for internal optimizations (i.e. StorageVersion API) and likely won't see too much use from users.