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
Make v1beta3 the default API version for clients #1986
Make v1beta3 the default API version for clients #1986
Conversation
0767b79
to
fed4e7a
Compare
[test] |
7bb9b2a
to
acb4351
Compare
@derekwaynecarr I ended up making the project admission control allow CREATE on an empty namespace in order to make cluster access review work (I currently have it as namespace scoped). We may end up needing to create a "both" scope... |
e28ba22
to
f7c6aab
Compare
@derekwaynecarr @deads2k review at your leisure, this is going in though. |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/1894/) (Image: devenv-fedora_1495) |
@liggitt did the UI test actually prevent me from breaking the UI?!?!?! |
shockingly, yes |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/2109/) |
267c934
to
343eed0
Compare
Need to figure out whether objects are safe enough.
Cluster access reviews are posting to an empty namespace
* Remove imageRepository* * Remove deployments * Fix a round trip error in output.to for ImageStreamTags
Output should default to ImageStreamTag in v1beta3 onward.
343eed0
to
f28b5ec
Compare
[merge] |
Evaluated for origin up to f28b5ec |
Merged by openshift-bot
First commit is in a different pull