kubernetes/website

Dynamic Admission Control: clarify exactly when failure policy Ignore is considered

Open

#33,039 opened on Apr 19, 2022

View on GitHub
 (14 comments) (1 reaction) (0 assignees)HTML (13,918 forks)batch import
help wantedlifecycle/frozentriage/accepted

Repository metrics

Stars
 (4,127 stars)
PR merge metrics
 (Avg merge 16d 13h) (160 merged PRs in 30d)

Description

I just observed that request the k8s API server can fail by rejecting admission controller even when the failure policy is ignore. It would be nice the documentation here to be enhanced and clearly state when the Ignore policy is used.

Particularly, it would be nice to be clarified which errors are unrecognized in this explanation:

failurePolicy defines how unrecognized errors and timeout errors from the admission webhook are handled.

A brief discussion on this subject matter can be found here

Contributor guide

Research direction
Review the current documentation at the referenced link and the Slack discussion to identify unclear parts. Propose specific wording changes to clarify when 'Ignore' failure policy applies.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Kubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80