-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Enable extensions/v1beta1/NetworkPolicy by default #28549
Enable extensions/v1beta1/NetworkPolicy by default #28549
Conversation
I still need to test this works. |
c381831
to
43d4ed2
Compare
GCE e2e build/test passed for commit 93c6e87374707772d2cec09b11c20d3f4b2ee835. |
GCE e2e build/test passed for commit c381831006d942068bc99e413541f3aa8bc3b695. |
GCE e2e build/test passed for commit 43d4ed233f552ae13cadc4f07397102534a0c1a8. |
I've tested that this works using the vagrant provider - the NetworkPolicy resource is indeed enabled by default. |
GCE e2e build/test passed for commit 53744f3e92532927894ff42fd47643d7cce56862. |
LGTM. @derekwaynecarr are you OK to review this or should we get someone else? We'll want to cherry-pick the min-set of this into 1.3.1. Jenkins says: Please run hack/update-api-reference-docs.sh @matchstick FYI |
53744f3
to
e9fbffd
Compare
e9fbffd
to
ea4be05
Compare
GCE e2e build/test passed for commit e9fbffdd98fb66762deaa0783fb7496606d81cd2. |
GCE e2e build/test passed for commit ea4be05. |
OK - auto generation completed and all checks passing :) What are we considering the minimum set that must be cherry-picked? It seems like there is a bunch of API documentation that wasn't generated the first time around for some reason that should probably be cherry picked as well. |
The min-set should be the master.go and docs. |
I think this will have to be a manual or semi-manual cherrypick |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit ea4be05. |
Automatic merge from submit-queue |
did we get a cherry-pick for this? |
@thockin - I don't think so. What is the process for a manual / semi-manual cherry-pick? Also, what is the process to get the API docs changes propagated through to kubernetes.io? |
@caseydavenport Cherrypick approved. Please create a cherrypick PR for this off the 1.3 release branch (not 1.3.0). Thank you. |
Fixes #28401
For some reason this also triggered an update to the swagger spec (which apparently hadn't been done before but wasn't failing validation...)