Skip to content
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

KMS v2 Improvements #3299

Open
1 of 4 tasks
ritazh opened this issue May 9, 2022 · 18 comments
Open
1 of 4 tasks

KMS v2 Improvements #3299

ritazh opened this issue May 9, 2022 · 18 comments
Assignees
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects

Comments

@ritazh
Copy link
Member

ritazh commented May 9, 2022

Enhancement Description

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 9, 2022
@ritazh
Copy link
Member Author

ritazh commented May 9, 2022

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 9, 2022
@enj enj added this to Needs Triage in SIG Auth May 13, 2022
@ritazh
Copy link
Member Author

ritazh commented May 31, 2022

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label May 31, 2022
@ritazh ritazh moved this from Needs Triage to In Review in SIG Auth May 31, 2022
@enj
Copy link
Member

enj commented Jun 6, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jun 6, 2022
@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 8, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 9, 2022

Hello @ritazh 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands: (updated on June 9, 2022)

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would need to update the following in the open KEP PR #3302:

For note, the status of this enhancement is marked as at risk. Thank you for keeping the issue description up-to-date!

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 17, 2022

Hello @ritazh 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get the pending items done before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT.

For note, the current status of the enhancement is atat-risk. Thank you!

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 21, 2022

With KEP PR #3302 merged, the enhancement is ready for 1.25 enhancements freeze.

For note, the status is now marked as tracked in the enhancements tracking sheet. Thank you!

@didicodes
Copy link

didicodes commented Jul 13, 2022

Hello @ritazh 👋, 1.25 Release Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for the 1.25 release. Please follow the steps detailed in the documentation to open a PR against the dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by August 4.


Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thank you!

@Atharva-Shinde
Copy link

Atharva-Shinde commented Jul 25, 2022

Hi @ritazh, Enhancements team here again 👋

Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure that the following items are completed before the code-freeze:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

Currently, the status of the enhancement is marked as at-risk

Thanks :)

@Atharva-Shinde
Copy link

Atharva-Shinde commented Aug 1, 2022

Hey @ritazh reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022.
Try to get the action items done which are mentioned in the comment above before the code-freeze :)
The status of the enhancement is still marked as at-risk

@ritazh
Copy link
Member Author

ritazh commented Aug 1, 2022

Thanks @Atharva-Shinde! kubernetes/kubernetes#111126 is currently waiting to be reviewed again by the approvers.

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 3, 2022

Hello 👋, 1.25 Enhancements Lead here.

Unfortunately, this enhancement did not meet the code freeze criteria because there are still unmerged k/k code PRs.

If you still wish to progress this enhancement in v1.25, please file an exception request. Thank you so much!

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Aug 3, 2022
@Priyankasaggu11929 Priyankasaggu11929 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Aug 3, 2022
@ritazh
Copy link
Member Author

ritazh commented Aug 3, 2022

@Priyankasaggu11929 FYI the exception request has been approved. kubernetes/kubernetes#111126 (comment)

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Aug 4, 2022

Thanks for the update @ritazh.

With the k/k PR also merged, I am marking it as tracked for 1.25 release cycle. Thank you so much!

@Priyankasaggu11929 Priyankasaggu11929 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Aug 4, 2022
@Priyankasaggu11929 Priyankasaggu11929 added this to the v1.25 milestone Aug 4, 2022
@liggitt liggitt modified the milestones: v1.25, v1.26 Sep 1, 2022
@liggitt liggitt assigned ritazh and enj Sep 1, 2022
@enj enj added lead-opted-in Denotes that an issue has been opted in to a release stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Sep 8, 2022
@rhockenbury rhockenbury added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Sep 20, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Sep 22, 2022

Hello @ritazh 👋, 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 beta for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.26
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following before the enhancements freeze:

  • Complete the process of updating the KEP Readme according to the latest test plan, I see TBD in those sections of the readme.
  • Complete and merge the PRR for beta stage.
  • Update the stage and milestone to beta and 1.26 in the kep.yaml file.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Let us know if you have any queries. Thank you!

@aramase
Copy link
Member

aramase commented Sep 26, 2022

This enhancement is targeting for stage beta for 1.26 (correct me, if otherwise)

@parul5sahoo Thanks for reaching out. This enhancement will remain alpha in v1.26 and beta is planned for v1.27. We have merged a PR to update the milestones in the kep.yaml.

@aramase
Copy link
Member

aramase commented Oct 3, 2022

@parul5sahoo Is the change in kep.yaml #3551 sufficient? We have moved the beta milestone for this enhancement to v1.27.

@parul5sahoo
Copy link
Member

parul5sahoo commented Oct 4, 2022

@parul5sahoo Is the change in kep.yaml #3551 sufficient? We have moved the beta milestone for this enhancement to v1.27.

yes @aramase that works, I've updates the status for this KEP!

@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Oct 6, 2022
@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Graduating
SIG Auth
In Review
Development

No branches or pull requests

10 participants