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
ClusterTrustBundles (previously Trust Anchor Sets) #3257
Comments
/sig auth |
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 |
Hello @ahmedtd 👋, 1.26 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022. 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 |
I'm planning to address these issues today. |
@marosset #3258 has been approved by SIG Auth leads and PRR #3258 (comment) - we are just waiting on explicit |
With #3258 merged, I have this down as |
Hi @ahmedtd 👋, 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, please link all relevant k/k PRs in the initial issue description for tracking. As always, we are here to help should questions come up. Thanks! |
Hello @ahmedtd ! 👋🏾, @katmutua 1.26 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. |
Hi @ahmedtd👋, 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, it looks like the following PRs are open and need to be merged before code freeze:
As always, we are here to help should questions come up. Thanks! |
Hello 👋, 1.26 Enhancements Lead here. Unfortunately, this enhancement did not meet requirements for code freeze. /milestone clear |
Ah sounds good! I'll mark you as complete then. Thanks!! |
@ahmedtd Is the KEP updated to reflect the current state and implementation plan for v1.28? |
Hello @ahmedtd👋, Enhancements team here. Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 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 |
I will do the updates today. |
@Kasambx Can you clarify what you mean by "Answer the questions on the readme"? As far as I can tell, the testing section of KEP-3257 is up-to-date with the template, and I've filled out everything that's necessary on for Alpha stage. I was able to list the affected packages for the unit testing, but the testgrid tab where it's suggested that I gather the existing coverage data is so large that it just crashes a few seconds after it loads (at least for me). Update: I was able to pull the data by using IncludeFilterByRegex |
@Atharva-Shinde does this need anything else for 1.28? PRR is good for alpha. |
Hello @ahmedtd! 1.28 Docs Shadow here. Does this enhancement work planned for 1.28 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hey @ahmedtd , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
Hey again @ahmedtd 👋 Just checking in as we approach Code freeze at 01:00 UTC Wednesday, 19th July 2023 . Here’s the enhancement’s state for the upcoming code freeze:
For this enhancement, it looks like the following code related PR is open and it needs to be merged or should be in merge-ready state before the code freeze commences : This is the code related PR that I found on this KEP issue Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
Hello @ahmedtd 👋, 1.28 Enhancements Lead here. Unfortunately, the implementation (code related) PR associated with this enhancement was not in the merge-ready state by code-freeze and hence this enhancement is now being removed from the v1.28 milestone. If you still wish to progress this enhancement in v1.28, please file an exception request. Thanks! /milestone clear |
Enhancement Description
One-line enhancement description (can be used as a release note): Define ClusterTrustBundle, a resource for holding X.509 trust anchors
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/3257-trust-anchor-sets/
Discussion Link: Draft doc w/ comments SIG Auth Meeting
Primary contact (assignee): @ahmedtd
Responsible SIGs: sig-auth
Enhancement target (which target equals to which milestone):
1.27 - Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):1.28 - Alpha
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: