DevOps Tutorials, Guides & Best Practices

The Google Cloud CLI is the command-line toolkit behind gcloud. Install it before you automate Google Cloud projects, authenticate service accounts, inspect IAM, or run deployment scripts from a terminal.

For the broader route map, see our GCP services for DevOps engineers guide.

Quick takeaway: use Google’s current installer for your operating system, verify with gcloud version, then run gcloud init before connecting real projects. Do not copy old “Cloud SDK” package snippets without checking the official docs first.

This guide keeps the flow practical: install on Linux or Windows, confirm the PATH, initialize the CLI, and fix the issues that usually block a first setup.

What Google Cloud CLI Includes

The package is now branded as the Google Cloud CLI. Older articles and scripts may still say “Google Cloud SDK”, but in daily work you mostly interact with these commands:

If you also work across AWS, keep the setup pattern similar to the AWS CLI workflow guide: install from the official source, verify the binary, configure auth, then test a read-only command before doing anything destructive.

Before You Install

Do these checks first, especially on shared laptops, CI runners, or machines that already have an older SDK installed.

• Confirm whether you need a user login, a service account, or both. gcloud init is user-friendly for local machines; service accounts are usually better for CI.
• Check whether your company blocks browser-based OAuth from terminals. If it does, plan a device-flow or service-account path.
• Decide whether you want a per-user install or a package-manager install. Package managers are easier to update across fleets; the archive installer is often simpler for one machine.
• Use the official Google Cloud docs as the source of truth because package names and setup commands change over time.

Install Google Cloud CLI on Linux

Google documents several Linux paths. The safest default for most engineers is to follow the official package-manager instructions for your distribution, then verify the installed binary.

Option 1: Package Manager Install

Use this path when you want normal system updates and a repeatable setup on workstations or build images. Google’s Linux package instructions cover repository setup, package installation, and component management.

# Follow the current Google Cloud package instructions for your distro first.
# After installation, verify the CLI is available.
gcloud version

# Start the interactive setup.
gcloud initCode language: PHP (php)

Option 2: Archive Install

Use the archive installer when you do not want to modify system package repositories, or when you need a user-local install. Download the current Linux archive from Google’s install page, extract it, then run the bundled installer.

tar -xf google-cloud-cli-*.tar.gz
./google-cloud-sdk/install.sh

# Restart the shell or source the updated profile, then verify.
gcloud versionCode language: PHP (php)

If gcloud is not found after install, open a new terminal first. If it still fails, inspect your shell profile and PATH entry before reinstalling.

Install Google Cloud CLI on Windows

On Windows, the simplest path is the official Google Cloud CLI installer. It can add the CLI to PATH and open an initialization flow after installation.

• Download the current Windows installer from Google’s install page.
• Run the installer with the default PATH option unless your team has a stricter workstation policy.
• Open a new PowerShell window after installation.
• Run gcloud version, then gcloud init.

gcloud version
gcloud init

If PowerShell cannot find the command, close and reopen the terminal. If that does not work, check the user PATH and confirm the Google Cloud CLI bin directory was added by the installer.

Initialize gcloud and Set the Active Project

gcloud init connects your local CLI to a Google account, creates or selects a configuration, and sets a default project. For a first local setup, that is usually enough.

gcloud init

# Confirm the active account and project.
gcloud auth list
gcloud config list

# Set a project explicitly if needed.
gcloud config set project PROJECT_IDCode language: PHP (php)

For automation, do not rely on whichever account happens to be active in your shell. Use explicit project IDs, named configurations, and service-account authentication where appropriate.

Common Install Problems and Fixes

Safe Verification Commands

After installation, test read-only commands before creating resources. This is the same safety habit you would use for CI/CD pipeline changes or cross-cloud automation.

gcloud version
gcloud auth list
gcloud config list
gcloud projects list --limit=5Code language: PHP (php)

If these commands work and the active project is correct, you can move on to service-specific commands. If they fail, fix authentication or project selection first. Do not troubleshoot by granting broader permissions until you know which identity the CLI is using.

When to Use Service Accounts Instead

A personal login is fine for local learning and one-off admin work. CI/CD, scheduled jobs, and production automation should normally use service accounts with scoped permissions. That keeps activity auditable and avoids tying automation to one person’s browser session.

For access-heavy work, keep Google Cloud IAM changes as deliberate as you would for AWS Organizations or IAM changes. If you are documenting multi-account controls, the same principle applies: auth setup is not just a convenience step, it is a blast-radius decision.

FAQ

These are the setup questions that usually come up after the base install works.

Sources

• Google Cloud CLI install documentation
• Google Cloud CLI Linux and Windows install quickstart
• Google Cloud CLI initialization documentation