Handling undecryptable resources

[stlaz]

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
  • KEP (k/enhancements) update PR(s): KEP-3926: handling undecryptable resources #3927
  • Code (k/k) update PR(s):
  • Docs (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.

[stlaz]

/sig auth
/sig api
/assign

[k8s-ci-robot]

@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.

[stlaz]

/sig api-machinery

[k8s-triage-robot]

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

[stlaz]

/remove-lifecycle stale

[sanchita-07]

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]

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]

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]

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!

[katcosgrove]

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]

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]

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]

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