-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Graduate server side validation to beta #110178
Graduate server side validation to beta #110178
Conversation
/triage accepted |
cd37a4a
to
8db54c1
Compare
8716ff1
to
54d1a55
Compare
54d1a55
to
eaa42a1
Compare
/retest |
43a3a8b
to
a8ab2dd
Compare
/assign @liggitt |
test/e2e/kubectl/kubectl.go
Outdated
{ | ||
"apiVersion": "apps/v1", | ||
"kind": "Deployment", | ||
"metadata": { | ||
"name": "my-dep", | ||
"namespace": "%s", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this change required? I don't remember this bit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it because of #110509
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, huh... should it have been added in #110509 then? I just wanted to make sure it wasn't newly required because of the server-side field validation feature defaulting on
if this test passes without this change, let's hoist this namespace addition to a separate PR to avoid entangling an unrelated fix in the feature enablement PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I've removed it.
I'm trying to remember if it was actually needed or not. I went through the PR CI history, and it doesn't seem like the test was actually breaking because of this.
Also, looking at #110509, the error there was from hardcoding the namespace not omitting it. If this PR passes without it, I don't think we need it.
I think maybe I just got nervous seeing a kubectl call in an e2e test I was working on without the namespace set and just added it to be safe, but I don't think it's actually necessary
a8ab2dd
to
6e6e60b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL @liggitt
test/e2e/kubectl/kubectl.go
Outdated
{ | ||
"apiVersion": "apps/v1", | ||
"kind": "Deployment", | ||
"metadata": { | ||
"name": "my-dep", | ||
"namespace": "%s", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it because of #110509
6e6e60b
to
d815449
Compare
last two commits (feature enablement and test addition) this PR adds on top of #109494 lgtm /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kevindelgado, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/retest kubectl wait unit test flake is an unrelated known issue |
/retest |
1 similar comment
/retest |
/kind feature |
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
1 similar comment
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Graduate server side field validation to beta and enable it by default.
All kubectl requests that set
--validate=true
by default will do so via strict server-side rather than client-side (for all requests targeting clusters with this feature enabled).The apiserver will default to warning on unknown/invalid fields unless strict or ignore validation is requested.
Which issue(s) this PR fixes:
Refers to: kubernetes/enhancements#2885
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: