"gcloud components install kubectl" should add it also to the PATH

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run "gcloud components install kubectl" on a container-vm instance
2. run "kubectl"

What is the expected output? What do you see instead?
- kubectl should be recognised as a command
- there should be a symlink installed in /usr/local/bin like there is with 
other executables from the SDK

What is the output of 'gcloud info'?
- any version/configuration up to the current one (0.9.88)

To avoid this I have to use startup scripts and run:

PATH="$PATH:$(gcloud info --format='value(config.paths.sdk_bin_path)')"
echo "" >> /etc/profile
echo "# added by the Google startup script" >> /etc/profile
echo "export PATH=$PATH" >> /etc/profile

Original issue reported on code.google.com by gabipetr...@gmail.com on 25 Nov 2015 at 5:20

[GoogleCodeExporter]

Thanks for the suggestion!

This is by design in the Cloud SDK. The installation is contained entirely 
within the google-cloud-sdk directory; the gcloud component manager is agnostic 
to the operating-system's package management system, and adding symlinks to 
global bin directories falls outside of the scope of the Cloud SDK.

This is really an issue with the integration between the Cloud SDK and 
container-vm instances. I'll raise this concern with those folks.

Original comment by z...@google.com on 25 Nov 2015 at 9:08

• Changed state: WorkingAsIntended