A user types:
kubectl get $resource
This will cause the bash completions to suggest the possible objects the
user can ask for. The complete list right now is:
endpoints
event
limitrange
namespace
node
persistentvolume
persistentvolumeclaim
pod
replicationcontroller
resourcequota
secret
service
status
But this list should stay up2date as api objects are added or deleted
These functions call out to kubectl to get information about running
resources. They give us completions which are kubernetes aware and thus
obviously better than just cobra subcommands and flags.
Right now, our doc generation scripts notice if you make changes and
don't regen docs, don't include new docs, etc. But they miss it if your
changes should have REMOVED a doc. Both kubectl-apiversion and
kubectl-clusterinfo should have been removed, but weren't.
This patch starts tracking all generated doc files and will cause
problems if files should be removed and aren't.
apiserver becomes kube-apiserver
controller-manager -> kube-controller-manager
scheduler and proxy similarly.
Only thing I promise is that right now hack/build-go.sh and
build/release.sh exit with 0. That's it. Who knows if any of this
actually works....
add flags for namespace
add get events
add log
remove 'table' output format
add 'templatefile' output format
add 'apply' (but pretend createall doesn't exist becaues it sux when you
want to complete on just 'create')
Support pre command flags:
--api-version=
-a, --auth-path=
--certificate-authority=
--client-certificate=
--client-key=
--insecure-skip-tls-verify=
--match-server-version=
-s, --server=
And commands:
get
describe
create
update
delete
Tries to be smart about things like
kubectl get -o template requires a template file
It also tries to accept both sigular and plural versions of all
resources. Even though it will only complete to the plural version.
Brendan Burns