Adding clusters to the list of valid resources printed by kubectl help#31719
Conversation
|
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
1 similar comment
|
Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test". This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. |
|
@k8s-bot ok to test |
|
Is this for 1.4? I only ask because it would be great if we just made the On Tue, Aug 30, 2016 at 2:05 PM, Kubernetes Submit Queue <
|
|
Yes, I could not get to the transition to API discovery in 1.4, so sent this for 1.4. |
| // and add a short forms entry in expandResourceShortcut() when appropriate. | ||
| // TODO: This should be populated using the discovery information from apiserver. | ||
| valid_resources = `Valid resource types include: | ||
| * clusters (valid only when talking to federation apiserver) |
There was a problem hiding this comment.
(valid only for federation apiservers)
reads a bit better. "talking" is awkward in some contexts.
0a55b6f to
0fcbde5
Compare
|
Updated code as per comment, PTAL |
|
Reviewed 1 of 1 files at r2. Comments from Reviewable |
|
Adding the LGTM label as per comment from @jlowdermilk above. |
|
GCE e2e build/test passed for commit 0fcbde5. |
|
Automatic merge from submit-queue |
Ref #25592
Adding clusters to the list of valid resources printed by kubectl help with a clear message that it only works when talking to federation apiserver.
In future, we should replace the hard coded list with a dynamic list generated using APIServer's discovery API.
cc @kubernetes/kubectl @kubernetes/sig-cluster-federation
This change is