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
Client Exec Proxy #2718
Comments
/sig auth |
A KEP to propose a client-side proxy for a number of client authentication use cases.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
A KEP to propose a client-side proxy for a number of client authentication use cases.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
/remove-lifecycle rotten |
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
Quick reminder - Enhancement freeze is about a week away. If you are still looking to get this enhancement into v1.26, please plan to get #2693 merged before enhancement freeze. |
A KEP to propose a client-side proxy for a number of client authentication use cases.
A KEP to propose a client-side proxy for a number of client authentication use cases.
@rhockenbury #2693 has been approved by SIG Auth leads and PRR #2693 (comment) - we are just waiting on explicit |
@rhockenbury and now #2693 is merged 😄 |
Hey @enj, It looks like the KEP readme needs a few updates to comply with the latest test plan template, specifically around the Test Plan section. I'm going to mark this as |
@nckturner Are docs required for this KEP? If so, who will be opening the docs PR for |
Hi @nckturner 👋, Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, I do not see any k/k PRs linked to this issue. As always, we are here to help should questions come up. Thanks! |
Hi @nckturner 👋 1.26 Release Docs shadow here. This enhancement is marked as |
/milestone v1.27 Pushing this out to next release as we are out of time in v1.26. |
/label tracked/no |
Hello @nckturner 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
A KEP to propose a client-side proxy for a number of client authentication use cases.
Hi @nckturner 👋, Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:
Please let me know if there are any PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
/milestone clear We'll pick this back up next release. |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: