-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
update KEP 740 #4852
update KEP 740 #4852
Conversation
Welcome @HarshalNeelkamal! |
Hi @HarshalNeelkamal. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
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.
One high-level point of discussion... does this need any feature gates? It seems like it is explicitly controlled by a kube-apiserver flag, so there's no point in additionally adding a feature gate.
/ok-to-test |
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.
First pass.
|
||
No. | ||
|
||
### Monitoring Requirements |
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.
Need to fill out this section. Maybe we would want some part of this in the kube audit logs?
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.
Waiting until beta to release to fill it out. Let me know if you think we need it sooner?
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.
have filled the parts that I could. Would add the remaining after starting implementation. Might need benchmarking on SLIs.
#740 (comment) |
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 few minor nits from PRR
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 PRR for alpha looks good
/approve
- Create a cluster with ExternalJWTSigner configured. | ||
- Request a token for a service account principal. | ||
- Use a token as bearer for making requests to kube-apiserver and ensure it succeeds. |
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.
no change needed, just FYI, but integration tests will be way easier to test... to configure this for an e2e, we'd have to set up a completely new job with the cluster configured this way
See the KMS e2e tests:
- Their own job config: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-auth/sig-auth-encryption-at-rest.yaml
- Their own e2e setup: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/testing-manifests/auth/encrypt/run-e2e.sh
- Their own buildable binary mock provider: https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/kms/internal/plugins/_mock
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.
Ack
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 would still expect an e2e like the encrypt-all-kind one to exercise all the wiring, but I would expect ~95% of the testing to be done via unit/integration tests.
once you do the final sweep, also run |
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.
Second pass.
|
||
The Feature would not be used by workload directly but will be used by kube-apiserver. | ||
|
||
The usage should be visible to the operator using Audit logs. |
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.
Please be more specific.
f3eeecd
to
8284baa
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enj, HarshalNeelkamal, soltysh 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 |
One-line PR description: Update KEP for External ServiceAccount JWT signing
Issue link: API for external signing of Service Account tokens #740
Other comments:
provisional
in KEP-740: fix incorrect status #3653 due to being stale for over 3 years.