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

Handling undecryptable resources #3926

Open
1 of 4 tasks
stlaz opened this issue Mar 27, 2023 · 16 comments
Open
1 of 4 tasks

Handling undecryptable resources #3926

stlaz opened this issue Mar 27, 2023 · 16 comments
Assignees
@stlaz
Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth.

Comments

@stlaz
Copy link
Member

stlaz commented Mar 27, 2023 •
edited

Handling undecryptable resources

  • One-line enhancement description (can be used as a release note): Improve the identification of resources that won't decrypt. Make it possible to remove undecryptable resources by using the API.
  • Kubernetes Enhancement Proposal: KEP-3926: handling undecryptable resources #3927
  • Discussion Link: sig-auth meeting, 01.03.2023 - 40:41
  • Primary contact (assignee): @stlaz
  • Responsible SIGs: sig-auth, sig-api-machinery
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.28 (?)
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 27, 2023
@stlaz
Copy link
Member Author

stlaz commented Mar 27, 2023

/sig auth
/sig api
/assign

@k8s-ci-robot k8s-ci-robot added the sig/auth Categorizes an issue or PR as relevant to SIG Auth. label Mar 27, 2023
@k8s-ci-robot
Copy link
Contributor

@stlaz: The label(s) sig/api cannot be applied, because the repository doesn't have them.

In response to this:

/sig auth
/sig api
/assign

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.

@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 27, 2023
@stlaz
Copy link
Member Author

stlaz commented Mar 27, 2023

/sig api-machinery

@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Mar 27, 2023
@stlaz stlaz mentioned this issue Mar 27, 2023
Merged
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Jun 25, 2023
@stlaz
Copy link
Member Author

stlaz commented Jun 29, 2023

/remove-lifecycle stale

@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 Jun 29, 2023
@enj enj added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 7, 2023
@enj enj added this to the v1.29 milestone Sep 7, 2023
@sanchita-07
Copy link
Member

Hello @stlaz 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (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.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would need to add/update the following:

  • The status should be marked as implementable in the kep.yaml file.
  • Ensure the KEP readme using the latest template has been merged into the k/enhancements repo
  • Ensure that the PR including the production readiness review has been merged into k/enhancements.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.
Thank you!

@sanchita-07
Copy link
Member

Hi @stlaz , checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze. It looks like #3927 will address the requirements. Let me know if I missed anything. Thanks!

@stlaz
Copy link
Member Author

stlaz commented Oct 5, 2023

Hello 👋
Indeed, #3927 should indeed address the requirements. I'm trying to move it forward but it's not yet clear if it'll make it in time.

@npolshakova
Copy link

With KEP PR #3927 approved, the enhancement is ready for the enhancements freeze. The status is now marked as tracked for enhancement freeze for 1.29. 🚀 Thank you!

@stlaz stlaz mentioned this issue Oct 6, 2023
Merged
@katcosgrove
Copy link

Hey there @stlaz! 👋, v1.29 Docs Lead here.
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

@katcosgrove
Copy link

Hi again @stlaz ! The deadline to open a placeholder PR against k/website for required documentation is this Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you!

@stlaz
Copy link
Member Author

stlaz commented Oct 19, 2023

Hello,
Sorry for late reply. Unfortunately, due to external circumstances, we won't be able to deliver the work for the 1.29 milestone 😞

@npolshakova
Copy link

Hi @stlaz, 1.29 Enhancements team here- thanks for letting us know, I'll remove this KEP from the tracking board.
/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.29 milestone Oct 20, 2023
@salehsedghpour
Copy link
Contributor

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Jan 6, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Apr 5, 2024
@stlaz
Copy link
Member Author

stlaz commented Apr 17, 2024

/remove-lifecycle stale

@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 Apr 17, 2024
@stlaz stlaz mentioned this issue May 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stlaz stlaz

Labels
sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth.
Projects
1.29 Enhancements Tracking
Status: Removed from Milestone
SIG Auth
Status: In Review
Milestone
No milestone
Development

No branches or pull requests
8 participants
@stlaz @enj @npolshakova @k8s-ci-robot @katcosgrove @salehsedghpour @k8s-triage-robot @sanchita-07