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.

Sign up for GitHub

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

Jump to bottom

KMS Observability #3130

Closed
4 tasks
aramase opened this issue Jan 12, 2022 · 16 comments
Closed
4 tasks

KMS Observability #3130

aramase opened this issue Jan 12, 2022 · 16 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/auth Categorizes an issue or PR as relevant to SIG Auth. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
SIG Auth Old

Comments

@aramase
Copy link
Member

aramase commented Jan 12, 2022

Enhancement Description

  • One-line enhancement description (can be used as a release note): KMS-Plugin observability enhancements
  • Kubernetes Enhancement Proposal:
  • Discussion Link:
  • Primary contact (assignee): @aramase
  • Responsible SIGs: sig-auth
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.24
    • Beta release target (x.y): 1.25
    • Stable release target (x.y): 1.26
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 12, 2022
@aramase
Copy link
Member Author

aramase commented Jan 12, 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 Jan 12, 2022
@aramase aramase mentioned this issue Jan 13, 2022
Merged
@gracenng gracenng added this to the v1.24 milestone Jan 20, 2022
@gracenng gracenng added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 20, 2022
@gracenng
Copy link
Member

Hi @aramase ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd. This enhancements is targeting alpha for 1.24
Here’s where this enhancement currently stands:

  • Updated KEP file using the latest template has been merged into the k/enhancements repo. -- please add milestone field in kep.yaml
  • KEP status is marked as implementable for this release with latest-milestone: 1.24
  • KEP has a test plan section filled out.
    - [ ] KEP has up to date graduation criteria. not needed for alpha
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is track as at risk
Thanks!

@enj enj added this to Needs Triage in SIG Auth Old Jan 24, 2022
@gracenng
Copy link
Member

Hi @aramase , 1.24 Enhancements Team here.

Reaching out as we're less than a week away from Enhancement Freeze on Thursday, February 3rd.
I'm current awaiting #3133 to merge and current status is at risk

@ritazh ritazh moved this from Needs Triage to In Review in SIG Auth Old Jan 31, 2022
@gracenng
Copy link
Member

gracenng commented Feb 4, 2022

All good for 1.24 Enhancements Freeze

@chrisnegus
Copy link

Hi @aramase 👋 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

@gracenng
Copy link
Member

Hi @aramase 1.24 Enhancements Team here,
With Code Freeze approaching on 18:00 PDT Tuesday March 29th 2022, the enhancement status is at risk as there is no linked k/k PR. Kindly list them in this issue. Thanks!

@enj enj modified the milestones: v1.24, v1.25 Mar 21, 2022
@enj
Copy link
Member

enj commented Mar 21, 2022

@gracenng we are going to move this out into v1.25 - please remove it from the v1.24 tracked enhancements. Thanks!

@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 Mar 23, 2022
@ritazh
Copy link
Member

ritazh commented Jun 6, 2022

/milestone clear
This can be closed once #3302 is merged.

@k8s-ci-robot
Copy link
Contributor

@ritazh: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone clear
This can be closed once #3302 is merged.

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/test-infra repository.

@enj
Copy link
Member

enj commented Jun 6, 2022

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Jun 6, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2022
@aramase
Copy link
Member Author

aramase commented Sep 6, 2022

/remove-lifecycle stale

This KEP has been replaced by https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3299-kms-v2-improvements. Should we close this issue?

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 6, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 5, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 4, 2023
@aramase
Copy link
Member Author

aramase commented Jan 4, 2023

This KEP has been replaced by https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3299-kms-v2-improvements

enhancements/keps/sig-auth/3299-kms-v2-improvements/kep.yaml

Lines 15 to 16 in 7a8706d

replaces:
- "/keps/sig-auth/3130-kms-observability"

Closing this issue as it's no longer active.

/close

@k8s-ci-robot
Copy link
Contributor

@aramase: Closing this issue.

In response to this:

This KEP has been replaced by https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3299-kms-v2-improvements

enhancements/keps/sig-auth/3299-kms-v2-improvements/kep.yaml

Lines 15 to 16 in 7a8706d

replaces:
- "/keps/sig-auth/3130-kms-observability"

Closing this issue as it's no longer active.

/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/auth Categorizes an issue or PR as relevant to SIG Auth. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
SIG Auth
Archived in project
SIG Auth Old
In Review
Milestone
No milestone
Development

No branches or pull requests
8 participants
@ritazh @enj @aramase @chrisnegus @k8s-ci-robot @Priyankasaggu11929 @gracenng @k8s-triage-robot