Ahmet Alp Balkan
Ahmet Alp Balkan
Whats your need for this?This is an intentional design choice because we install a single symlink. I don't understand why would you install a subcommand just by itself instead of...
Which "kubectl node" command are you referring to? Does the kubectl core now allow adding plugins to arbitrary builtin subcommands?
I don't think you can add subcommands to a builtin command (except for "create")? Is there actually a "kubectl node" command, if not, we don't grant a name like that...
/hold Let's discuss the design first and agree on the need.
@marquiz any ideas why the logs show "timeout" for informer sync many minutes later the logs say "node updated"? I'm trying to understand if logs show any indication of cache...
> That DOES block until the caches have synced. However, in v0.16.0 we don't call `WaitForCacheSync()` @marquiz thanks for the responses. Would the lack of `WaitForCacheSync()` combined with something like...
I can closr in favor of #107 although this has a bit more rationale/explanation.
:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- Thanks for submitting your kubectl plugin to Krew! One of the krew-index maintainers will review it soon....
view-secret plugin already does this I think.