Is this for admission webhooks only, or for all HTTP callouts (eg https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#imagepolicywebhook and https://kubernetes.io/docs/reference/access-authn-authz/webhook/)?

@sftim this is only for admission webhooks (updated the title). We've also had conversations about doing something similar for authorization webhooks, but that will probably be folded in with #3221

Is there a KEP for this I can review for PRR?

Hello @tallclair 👋, v1.27 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (please 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.27
• 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 enhancement, the first thing we need is access to the KEP so we can then confirm the rest.

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

@sftim this is only for admission webhooks (updated the title). We've also had conversations about doing something similar for authorization webhooks, but that will probably be folded in with #3221

If so, should this be tracked separately? I've confused about what I'm supposed to review for PRR here.

The problem was the original title - the rename fully addressed my concern.

If we want CEL conditions for admission authz webhooks, that change won't be part of this KEP.

Hi @logicalhan , an update based on the linked KEP PR.

This enhancement is targeting for stage alpha for 1.27 (please correct me, if otherwise)

Here's where this enhancement currently stands, assuming #3717 in it's current state:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• 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 enhancement, the following would need to be updated, assuming #3717 in it's current state:

• Use the latest version of the template. There is an additional question on the Scalability section of the PRR, although in one that isn't mandatory for alpha, it would be a good time to add it and sync with the latest template structure.
• An updated Test Plan, with the sections filled.
• Up-to-date graduation criteria filled.

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

@fsmunoz Thanks for the list. The remaining items are addressed in #3861

@logicalhan sorry for missing your earlier questions! It looks like you figured it out, but please ping me on chat/slack if you have any outstanding questions.

Hello @tallclair , thank you.

I'm marking this as tracked with two comments:

• The Test Plan has TBD information that should be analysed and reviewed.
• The Graduation Criteria would benefit from including other stages, but it does contain the alpha one.

This enhancement is ready to be traced for graduation to alpha in v1.27

/stage alpha
/label tracked/yes

@fsmunoz: The label(s) /label stage/alpha cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

/stage alpha

Hello @tallclair 👋🏾 !

@katmutua 1.27 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

If you already have existing open PRs please link them to the description so we can easily track them. Thanks!

Hi @tallclair 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

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

For this enhancement, it looks like the following PRs need to be merged before code freeze:

• Matchconditions admission webhooks alpha implementation for kep-3716 kubernetes#116261

Please let me know what other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

This should be graduation criteria for beta: kubernetes/kubernetes#116588

@Atharva-Shinde @Rishit-dagli @aramase PR kubernetes/website#42060 is ready

/remove-label lead-opted-in

/label lead-opted-in
/milestone v1.30

Hello @tallclair, @jpbetz 👋, v1.30 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage stable for v1.30 (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.30. 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).

Almost everything is done in #4435. One minor change that we need to make is to update the stage to stable here

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!

Hello 👋, v1.30 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

#4435 hasn't updated the stage key to stable. It still says beta.

This is a small fix, so please file an exception request. Thanks!

/milestone clear

Just raised a PR: #4513

Hello @tallclair 👋, 1.30 Docs Shadow here.
Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

(At a minimum, please remember to update the feature flags to stable for this release ✨)

Hi @tallclair,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

/assign @ivelichkovich

Igor, can you take a look at the docs & comms requests above?

Hey again @tallclair, @jpbetz 👋 v1.30 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the issue description to include all the related PRs of this KEP):

• kep-3716 GA, remove feature gate kubernetes#123560

Currently, I'm marking this KEP as At Risk for Code Freeze. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

@tallclair, @jpbetz: Are all the code PRs for this KEP merged? Are there any other PRs we should track other than kubernetes/kubernetes#123560?

Are all the code PRs for this KEP merged? Are there any other PRs we should track other than kubernetes/kubernetes#123560?

Yes. These two PRs were merged to complete the GA promotion:

• kep-3716 GA, remove feature gate kubernetes#123560
• promote match conditions e2e tests to conformance kubernetes#123564

I've added them to the issue description as well (I also added the doc placeholder PR).

Let us know if you see anything missing, our understanding is that this enhancement is fully graduated and should be tracked as such at part of 1.30. Thanks!

Thank you @jpbetz!

With all the implementation (code related) PRs merged as per the issue description:

• kep-3716 GA, remove feature gate kubernetes#123560
• promote match conditions e2e tests to conformance kubernetes#123564

This enhancement is now marked as tracked for code freeze for the 1.30 Code Freeze!

Raised a docs PR ready to review for this: kubernetes/website#45525