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.

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

Validation unify all #6

Open
wants to merge 1,106 commits into
base: liggitt-json-stdlib
Choose a base branch
from
Open

Conversation

kevindelgado
Copy link
Owner

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@kevindelgado kevindelgado force-pushed the validation-unify-all branch 2 times, most recently from f0caae4 to 8bc736a Compare October 20, 2021 21:09
@kevindelgado kevindelgado force-pushed the validation-unify-all branch 2 times, most recently from e8b931a to dd91910 Compare October 28, 2021 01:11
@kevindelgado kevindelgado force-pushed the validation-unify-all branch 8 times, most recently from 5b9c077 to 43a17e1 Compare November 10, 2021 07:09
jpbetz and others added 18 commits November 10, 2021 13:15
…Lifecycle

Changed code to improve output for files under test/e2e/lifecycle
kubeadm: fix inverted warning message
…rocessTestFromOrphans

fish out ShareProcessNamespace from orphans tab
kubeam:node-proxier -> kubeadm:node-proxier
This causes e2e test failures:
"[area-kubeadm] proxy addon kube-proxy ServiceAccount should
be bound to the system:node-proxier cluster role"

in:
- kubeadm-kinder-latest
- kubeadm-kinder-latest-on-...
- other tests
…ePages

The DownwardAPIHugePages feature is beta now, set true by default.
…sGateNodeConformance

PodReadinessGate is stable feature and test runs all green
@kevindelgado kevindelgado force-pushed the validation-unify-all branch 16 times, most recently from 8cd4bf0 to bea263b Compare November 19, 2021 20:21
Implements server side field validation behind the
`ServerSideFieldValidation` feature gate. With the
feature enabled, any create/update/patch request
with the `fieldValidation` query param set to
"Strict" will error if the object in the request
body have unknown fields. A value of "Warn"
(also the default when the feautre is enabled)
will succeed the request with a warning.

When the feature is disabled (or the query param
has a value of "Ignore"), the request will succeed
as it previously had with no indications of any
unknown or duplicate fields.
kevindelgado added a commit that referenced this pull request Apr 28, 2022
* discovery client hash for GroupVersionForDiscovery

* Update generated files

* update compatibility fixture data
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet