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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

馃摉 add link from k8s to clarify admission webhooks #3648

Merged
merged 1 commit into from
Oct 4, 2023
Merged

馃摉 add link from k8s to clarify admission webhooks #3648

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/book/src/reference/admission-webhook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Admission Webhooks

Admission webhooks are HTTP callbacks that receive admission requests, process
[Admission webhooks][k8s-doc-admission-webhooks] are HTTP callbacks that receive admission requests, process
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

them and return admission responses.

Kubernetes provides the following types of admission webhooks:
Expand Down Expand Up @@ -98,4 +98,6 @@ spec:

While certain edge scenarios might allow a mutating webhook to seamlessly modify the status, treading this path isn't a
universally acclaimed or recommended strategy. Entrusting the controller logic with status updates remains the
most advocated approach.
most advocated approach.

k8s-doc-admission-webhooks: https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks