-
Notifications
You must be signed in to change notification settings - Fork 38.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
fix the namespaceScoped of cachers #19970
fix the namespaceScoped of cachers #19970
Conversation
Labelling this PR as size/S |
It has caused a problem-- someone else has this same exact change out for review, but I can't find it now. In that review, I asked for it to use e.g. "pods.NamespaceScoped()" instead of "true", so that future copy-paste inheritence will be more likely to change it. But I can't find the PR now... |
587409d
to
f76a7ca
Compare
Labelling this PR as size/M |
@lavalamp, I've addressed your comment. PTAL. Thanks. |
GCE e2e test build/test passed for commit 587409d20bae136be00a7f093b94408ed8bfc835. |
GCE e2e test build/test passed for commit f76a7ca6e8f7e36aabd87699e2f2e80c56730edb. |
Thanks for doing this, was on call so didn't get a chance to address the review comments (#19663) but you can go ahead and get yours in. |
any chance you could include a test that would have caught the error? |
If you can add the test I'll add LGTM |
It's tricky to test this, since to be useful the test has to check resources that will be added in the future and that it therefore doesn't know about-- I suggested adding a check where REST objects are used that their storage & strategy scopes agree. |
@lavalamp, by actually doing this I found it perhaps is a bad idea. I pushed a second commit for the ease of discussion. See my comments in that commit for details. |
Instead of passing in the boolean to storage decorator, why not pass in the create strategy itself? Then someone has to provide a valid strategy, and you can ensure you test that NamespaceScoped is true. That would satisfy the test aspect for me. |
Or if not the create strategy, the |
Not sure what you mean by "sliced" but this sounds good to me. |
GCE e2e build/test failed for commit 46df6fb439843abc05516a267b2731077c1a1c20. |
46df6fb
to
ceb35eb
Compare
Sliced = a partial interface like:
that create strategy satisfies On Fri, Jan 22, 2016 at 5:05 PM, Kubernetes Bot notifications@github.com
|
ceb35eb
to
02b07c9
Compare
@smarterclayton yeah, I figured that out somehow. Could you take another look? Thanks. |
I feel more comfortable with this (you would have to provide a fake method, knowing that you have the strategy handy). No further comments. |
GCE e2e test build/test passed for commit fb9ac049752479332effb49f2382382446f0b495. |
@k8s-bot test this Tests are more than 48 hours old. Re-running tests. |
GCE e2e test build/test passed for commit ca3434d6350c497588eda19d10cc1eb729f92bb3. |
@k8s-bot test this Tests are more than 48 hours old. Re-running tests. |
GCE e2e test build/test passed for commit ca3434d6350c497588eda19d10cc1eb729f92bb3. |
GCE e2e test build/test passed for commit ca3434d6350c497588eda19d10cc1eb729f92bb3. |
PR needs rebase |
ca3434d
to
ebcff4b
Compare
Apparently you need a rebase |
GCE e2e build/test failed for commit ebcff4b. |
GCE e2e test build/test passed for commit ebcff4b. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e test build/test passed for commit ebcff4b. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
@caesarxuchao - thanks a lot for fixing it! |
UPSTREAM: 65001: Quiet verbose apiserver logs Origin-commit: b0ba202a287acf2ef6b77a9de8cfb3c6adaa369d
Fix #19939
It's strange that so many of them are misconfigured and haven't caused any problem so far.
@janetkuo