Getting GKE Kubernetes credentials#
To use the standard Kubernetes administrative command kubectl or other commands built on the same protocol (such as Helm or the Phalanx installer), you must have authentication credentials stored for the target Kubernetes cluster. Google provides a mechanism to obtain those credentials using the gcloud command:
Ensure you have a Google account with access to the Google Cloud Platform project where your target Kubernetes cluster is running. For Phalanx environments run by SQuaRE, this access must be via an
lsst.cloudGoogle account that is used only for Rubin activities. If you do not already have such an account or permissions and need administrative access to a Phalanx environment maintained by SQuaRE, contact SQuaRE for access.
Install gcloud on the system on which you want to run privileged Kubernetes commands.
Initialize gcloud. You will need to have access to the Google Cloud Platform project where your target Kubernetes cluster is running.
If you have access to multiple Google Cloud Platform projects, you will be asked to select one as your default project. You may wish to choose the project for the Phalanx environment you use most often. You can find the project ID of a Phalanx project hosted on GKE in its environments page.
Install kubectl and the GKE auth plugin. As part of that installation, you will run the gcloud command that obtains credentials usable by kubectl and other privileged Kubernetes commands.
The final step has an example gcloud command, but it assumes that you are getting credentials for your default project. Rubin uses multiple Google Cloud Platform projects for different environments, so you may have to provide the project ID as well. For the full command to run, see the bottom of the relevant environments page.
Once you have followed this process on a system, the credentials will remain valid unless the Kubernetes control plane credentials are rotated.
The Kubernetes control plane credentials eventually expire and have to periodically be rotated. If the control plane credentials of the Kubernetes cluster are rotated, you will have to re-run the gcloud command to refresh your credentials. If you discover that your credentials are no longer working, try that command and see if the problem persists.