{"id":810,"date":"2024-03-28T05:55:00","date_gmt":"2024-03-28T05:55:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=810"},"modified":"2024-03-28T05:55:00","modified_gmt":"2024-03-28T05:55:00","slug":"setup-google-cloud-clisdk","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=810","title":{"rendered":"How to Setup Google Cloud SDK – gcloud CLI Beginners Guide"},"content":{"rendered":"

If you want to interact with Google Cloud through gcloud CLI or through code, you need to setup the gcloud CLI & SDK on your workstation.<\/p>\n

For example, if you want to write a python script that interacts with google cloud, you should have the gcloud sdk installed so that all the required packages for python will be available for your script.<\/p>\n

This tutorial will guide you through the steps for setting up Google Cloud gcloud CLI SDK on your workstation.<\/p>\n

Also, I have added some of the tips and tricks that I have learned while using gcloud<\/code> CLI utility in my workstation.<\/p>\n

Install gloud CLI SDK<\/h2>\n
\n
Note:<\/strong><\/b> If you’re using a google cloud instance, SDK is installed by default.<\/div>\n<\/div>\n

Step 1:<\/strong> Head over to https:\/\/cloud.google.com\/sdk\/<\/a> <\/a>and copy the link to the appropriate installation package. This package is common for all Linux distributions.<\/p>\n

\n
For Windows users: Download the installation package from https:\/\/cloud.google.com\/sdk\/windows<\/a> and install it directly on your systems. You will have the gcloud command available in the terminal.<\/div>\n<\/div>\n

Step 2: <\/strong>Download the package.<\/p>\n

wget https:\/\/dl.google.com\/dl\/cloudsdk\/channels\/rapid\/downloads\/google-cloud-cli-470.0.0-linux-x86_64.tar.gz<\/code><\/pre>\n
Step 3: <\/strong>Untar the sdk package.<\/p>\n
tar -xvf google-cloud-sdk*<\/code><\/pre>\n
Step 4: <\/strong>Install the SDK using the install.sh<\/code> script. It will detect the appropriate package for your Linux distribution and installs it.<\/p>\n
.\/google-cloud-sdk\/install.sh<\/code><\/pre>\n
Step 5:<\/strong> Follow through the installation prompts and select the required options. It is pretty self-explanatory. It will take a couple of minutes for the setup.<\/p>\n
\"gcloud
Click to view in HD<\/span><\/figcaption><\/figure>\n
Step 6:<\/strong> Restart the terminal or source the .bashrc or .zshrc<\/strong> file based on the shell profile preference you chose during the installation.<\/p>\n
source ~\/.bashrc\nsource ~\/.zshrc<\/code><\/pre>\n
If you dont open a new terminal session or source the relevant shell profile, you might see the following error.<\/p>\n
-bash: gcloud: command not found<\/code><\/pre>\n
Step 7: <\/strong>Now, to validate the installation, open a new terminal session and execute the gcloud<\/code> command.<\/p>\n
$ gcloud --version\n\nGoogle Cloud SDK 470.0.0\nbq 2.1.2\ncore 2024.03.22\ngcloud-crc32c 1.0.0\ngsutil 5.27<\/code><\/pre>\n
Configuring gcloud CLI With Google Project<\/h3>\n
Now that we have the SDK installed, we need to configure the Google cloud SDK to talk to a specific project.<\/p>\n
We use the gcloud<\/code> utility from the installed SDK for CLI based google cloud access.<\/p>\n
Follow the steps given below to configure gcloud<\/code> with a specific google project.<\/p>\n
Step 1:<\/strong> Initialise the project configuration using the following command.<\/p>\n
gcloud init --console-only<\/code><\/pre>\n
Step 2:<\/strong> You will see the following prompt. Select “Y”.<\/p>\n
To continue, you must log in. Would you like to log in (Y\/n)? Y<\/code><\/pre>\n
\"google
Click to view in HD<\/span><\/figcaption><\/figure>\n
Copy and paste the URL in the browser. Then log in to your google cloud account and grant permissions to access google cloud resources.<\/p>\n
You will see a page with a token. Copy the token and enter in the terminal.<\/p>\n
Now you will be logged in, and you can select the project that you want to set as default, as shown in the image below.<\/p>\n
\"google
Click to view in HD<\/span><\/figcaption><\/figure>\n
Like this, you can add multiple gcloud configurations<\/a> if you work with multiple google cloud accounts. You can switch between different accounts. I have explained this in the next section.<\/p>\n
gcloud CLI SDK Auth Config Location<\/h2>\n
To know all the configuration location of gcloud CLI SDK, execute the following command.<\/p>\n
gcloud info<\/code><\/pre>\n
\"default
Click to view in HD<\/span><\/figcaption><\/figure>\n
All the SDK configs get stored in the .config<\/code> folder in your workstation home location.<\/p>\n
If I run a tree from the .config<\/code> folder, this is what I have. The JSON files under legacy_credentials have the client id <\/code>and client secret<\/code> to connect to the google cloud account.<\/p>\n
\"gcloud<\/figure>\n
Validate gcloud CLI Authentication<\/h2>\n
Now that we have a valid cloud configuration, let’s run some basic gcloud<\/code> CLI commands to verify the installation.<\/p>\n
Step 1:<\/strong> List the credential account.<\/p>\n
gcloud auth list<\/code><\/pre>\n
In my case, I have two google cloud accounts configured in my workstation. So it lists two accounts, and there is a *<\/code> in the active account.<\/p>\n
\"\"<\/figure>\n
When you have multiple gcloud<\/code> accounts, you can switch between accounts using the following command<\/p>\n
gcloud config set account account@devopscube.com<\/code><\/pre>\n
Step 2:<\/strong> To view your default gcloud<\/code> configs of the active configuration, use the following command.<\/p>\n
gcloud config list<\/code><\/pre>\n
You can also manually change the configuration by editing the config file from the ~\/.config\/gcloud\/configurations<\/code> folder.<\/p>\n
Sometimes when you have multiple accounts configured, there could be a mismatch between activated account and active configuration. To solve this, first list the configruations.<\/p>\n
gcloud config configurations list<\/code><\/pre>\n
\"list
Click to view in HD<\/span><\/figcaption><\/figure>\n
If there is a mismatch, you can activate the correct configuration using the following command, assuming you activate the default configuration.<\/p>\n
gcloud config configurations activate default<\/code><\/pre>\n
Step 3:<\/strong> To list all the gcloud<\/code> commands, use the following command.<\/p>\n
gcloud help<\/code><\/pre>\n
gcloud Cheat Sheet<\/h2>\n
Well, I don’t have any cheat sheet for gcloud<\/code>.<\/p>\n
However, there is a cool gcloud<\/code> cheat sheet command which displays the gcloud cheat sheet.<\/p>\n
gcloud cheat-sheet<\/code><\/pre>\n
Also you can use the cheat sheet from google cloud documentation<\/a>.<\/p>\n
Other gcloud Components<\/h2>\n
When you install the google SDK, only the core google cloud libraries get installed.<\/p>\n
But there are other components that are part of google cloud sdk.<\/p>\n
For example kubectl<\/code>. A utility required to interact with Google Kubernetes cluster<\/a>.<\/p>\n
To list all the available components execute the following command.<\/p>\n
gcloud components list<\/code><\/pre>\n
\"list
Click to view in HD<\/span><\/figcaption><\/figure>\n
Updating gcloud CLI Components<\/h2>\n
Updating gcloud CLI is pretty simple.<\/p>\n
Use the following one-line to update gcloud components.<\/p>\n
gcloud components update<\/code><\/pre>\n
Create a Google Compute Instance Using CLI<\/h2>\n
This section is only optional.<\/p>\n
If you want to have a little hands-on with the gcloud command-line utility, you can follow this section to create a compute instance, access it, and then delete it.<\/p>\n
To start with, we will create a instance using the CLI.<\/p>\n
Step 1:<\/strong> Get the list of images using the following command.<\/p>\n
gcloud compute images list<\/code><\/pre>\n
\"gcloud
Click to view in HD<\/span><\/figcaption><\/figure>\n
Step 2:<\/strong> The following command will create an f1 micro ubuntu instance with the ubuntu image from the highlighted image family.<\/p>\n
gcloud compute instances create devopscube-demo-instance \\\n --image centos-7-v20170523 \\\n --image-project centos-cloud --set-machine-type f1-micro --zone us-central1-a<\/code><\/pre>\n
There are so many flags associated with instance creations. Refer to this official documentation<\/a> for more information on the flags.<\/p>\n
Step 3: <\/strong>To connect the instance via ssh, just execute the following command. The gcloud<\/code> command will automatically create the ssh key in your ~\/.ssh folder if it doesn’t exist and connects to your instance.<\/p>\n
\n
Security Note:<\/strong><\/b> Do not deploy any public images in enterprise accounts even if you have permissions. Always use security-approved images in enterprise accounts to stay out of trouble.<\/div>\n<\/div>\n
gcloud compute ssh (instance-name)<\/p>\n
For example,<\/p>\n
gcloud compute ssh devopscube-demo-instance<\/code><\/pre>\n
Step 4:<\/strong> Delete the created instance using the following command.<\/p>\n
gcloud compute instances delete (instance name)<\/code><\/pre>\n
For example,<\/p>\n
gcloud compute instances delete devopscube-demo-instance<\/code><\/pre>\n
Conclusion<\/h2>\n
In this blog I have covered the steps to setup google cloud SDK and using it with gcloud CLI<\/p>\n
Hope it helped or you might have more tips that can add value to the existing content.<\/p>\n
Either way, please drop a comment.<\/p>\n
\n
Ngu\u1ed3n:<\/strong> How to Setup Google Cloud SDK – gcloud CLI Beginners Guide \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Source: https:\/\/devopscube.com\/setup-google-cloud-clisdk\/<\/p>\n","protected":false},"author":1,"featured_media":811,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-810","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=810"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/810\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/811"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=810"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=810"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}