Rebase onto Kubernetes 6241a21#1136
Conversation
|
[test] |
|
Needs #1135 fixed upstream (although patched here). |
|
Might fix #1115 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_openshift3/1219/) |
|
I cherry-picked Vish's change in as well. |
There was a problem hiding this comment.
Is it correct to be using the services strategy when validating pod name generation? In controllers/types.go they're technically the same strategy, just struck me as strange when reading it.
There was a problem hiding this comment.
Disregard, the next file removes the Pods strategy....
There was a problem hiding this comment.
I dunno, ask upstream.
On Feb 25, 2015, at 6:16 AM, Paul notifications@github.com wrote:
In Godeps/_workspace/src/github.com/GoogleCloudPlatform/kubernetes/pkg/api/rest/create_test.go:
@@ -25,17 +25,17 @@ import (
func TestCheckGeneratedNameError(t *testing.T) {
expect := errors.NewNotFound("foo", "bar")
- if err := CheckGeneratedNameError(Pods, expect, &api.Pod{}); err != expect {
- if err := CheckGeneratedNameError(Services, expect, &api.Pod{}); err != expect {
Is it correct to be using the services strategy when validating pod name generation? In controllers/types.go they're technically the same strategy, just struck me as strange when reading it.—
Reply to this email directly or view it on GitHub.
|
My eyes...they bleed! LGTM Some things that jumped out at me that may affect us:
I can no longer read any secrets code without picturing @pmorie standing behind me whispering "shhh!" |
|
The router is fixed in my last commit. Also, you don't have to review the merge commits :). Just my fixes.
|
4f08824 to
6e59b78
Compare
|
[test] |
|
I'll look at adding a proper error for #1135 today or Monday. I previously misunderstood and thought that self-linking was already tolerant upstream. The number of required changes is much smaller than I anticipated. Is there going to be a card for someone to take advantage of the generic registry stuff? |
…a0236f680ffa8e11037
6e59b78 to
d1659cb
Compare
|
@deads2k calling ResourceAccessReviews("") is disallowed now upstream (you can't invoke create on a namespace scoped resource with ""), which causes: My preference is to define GlobalResourceAccessReview() method that takes no namespace and does not set Namespace() on the Create method. Do you have an alternative suggestion? |
Empty namespace is now disallowed as an action (you must not invoke request.Namespace() if you don't want a namespace set).
Fix router integration test
I'd have both. A GlobalResourceAccessReview for cluster-admins who have rights to access resources across all namespaces and a ResourceAccessReview for project admins who only have rights to a single namespace. I had heard rumors that global objects were going to be eliminated... @derekwaynecarr Will we still have globally objects in a month? |
|
@smarterclayton fyi, I need the secrets stuff in this for #1208 |
|
Brenton is going to cut beta2 before this lands. Talk to him and make sure the other stuff for beta2 is ready to land. |
|
[merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_openshift3/1102/) (Image: devenv-fedora_966) |
|
Evaluated for origin up to 1c06be8 |
…-3-8 UPSTREAM: 58433: lstat with abs path of parent
Includes remote command execution and Docker caching