-
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
separate RootCAConfigMap from BoundServiceAccountToken and Beta #24909
Conversation
issue is opened here: kubernetes/enhancements#542 |
/cc @liggitt |
Deploy preview for kubernetes-io-master-staging ready! Built with commit d69bf37 https://deploy-preview-24909--kubernetes-io-master-staging.netlify.app |
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.
Thanks @zshihang
Here's some wording suggestions.
@@ -512,6 +514,8 @@ Each feature gate is designed for enabling/disabling a specific feature: | |||
the input Pod's cpu and memory limits. The intent is to break ties between | |||
nodes with same scores. | |||
- `ResourceQuotaScopeSelectors`: Enable resource quota scope selectors. | |||
- `RootCAConfigMap`: Enable kube-controller-manager to publish a "kube-root-ca.crt" ConfigMap to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. |
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.
Hi. I'd write this as:
- `RootCAConfigMap`: Enable kube-controller-manager to publish a "kube-root-ca.crt" ConfigMap to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. | |
- `RootCAConfigMap`: Configure the kube-controller-manager to publish a {{< glossary_tooltip text="ConfigMap" term_id="configmap" >}} named `kube-root-ca.crt` to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. |
How does that look?
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.
done
@@ -512,6 +514,8 @@ Each feature gate is designed for enabling/disabling a specific feature: | |||
the input Pod's cpu and memory limits. The intent is to break ties between | |||
nodes with same scores. | |||
- `ResourceQuotaScopeSelectors`: Enable resource quota scope selectors. | |||
- `RootCAConfigMap`: Enable kube-controller-manager to publish a "kube-root-ca.crt" ConfigMap to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. | |||
See [Bound Service Account Tokens](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/1205-bound-service-account-tokens/README.md) for more details. |
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.
Can we copy the relevant text from that KEP into pages inside https://kubernetes.io/docs/reference/access-authn-authz/ ?
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 agree the content should be in the website. I'd actually add it to https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection
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.
That's a good idea too.
(I'm not keen on making task pages the only place to learn about features, because those can be hard to discover).
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 to access-authn-authz/service-accounts-admin.md
/sig auth |
/milestone 1.20 |
based on the comment that you linked, I am wondering if this should be pointed to |
the RootCAConfigMap is separated from BoundServiceAccountToken and we would like to document it. BoundServiceAccountToken is deferred to 1.21 this PR is merged kubernetes/kubernetes#96197 |
got it, thanks for the clarification @zshihang |
/assign |
Hi @zshihang, just wanted to follow up to remind you to look into the suggested changes. I believe this PR can be merged as soon as the feedbacks are addressed. Thank you! |
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 0b4952d https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5fab1fd6acb62d0008eed78b |
/lgtm |
LGTM label has been added. Git tree hash: f9ffb0e454b4734dd57e89f5a96418005b26c60d
|
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irvifa 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 |
separate RootCAConfigMap from BoundServiceAccountToken, see #24854 (comment)