Update gcloud version

[tekante]

Summary by CodeRabbit

• Chores
  • Updated Docker base image to the latest version.

[coderabbitai]

Walkthrough

The Dockerfile build stage base image is updated from Google Cloud CLI version 399.0.0 to 568.0.0, using Alpine Linux. The build stage alias remains unchanged.

Changes

Build stage base image update

Layer / File(s)	Summary
Build stage base image version bump src/Dockerfile	The build stage FROM directive is updated to use Google Cloud CLI version 568.0.0-alpine instead of 399.0.0-alpine.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump hops into view,
Google Cloud CLI shiny and new,
From 399 to 568 we climb,
Alpine still holds the line,
Fresher dependencies, just on time! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update gcloud version' directly corresponds to the main change in the changeset, which updates the gcloud Docker image from version 399.0.0 to 568.0.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-gcloud

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/Dockerfile (1)

1-8: ⚡ Quick win

Consider explicitly setting the non-root USER in this Dockerfile stage.

The base image gcr.io/google.com/cloudsdktool/google-cloud-cli:568.0.0-alpine already defaults to the non-root user "cloudsdk", so runtime will inherit that. However, since this is a multi-stage build, explicitly setting USER cloudsdk after the install/cleanup steps clarifies the runtime user and avoids ambiguity if subsequent stages reset it.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/Dockerfile` around lines 1 - 8, The Dockerfile's build stage currently
uses the google-cloud-cli Alpine image but doesn't explicitly set the non-root
user; after the install/cleanup RUN block that installs kubectl and
gke-gcloud-auth-plugin (the RUN that also removes python caches), add an
explicit USER cloudsdk declaration so the build stage (and any subsequent stages
that inherit it) clearly runs as the non-root "cloudsdk" user rather than
relying on the base image default.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/Dockerfile`:
- Around line 1-8: The Dockerfile's build stage currently uses the
google-cloud-cli Alpine image but doesn't explicitly set the non-root user;
after the install/cleanup RUN block that installs kubectl and
gke-gcloud-auth-plugin (the RUN that also removes python caches), add an
explicit USER cloudsdk declaration so the build stage (and any subsequent stages
that inherit it) clearly runs as the non-root "cloudsdk" user rather than
relying on the base image default.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 33cd183c-482b-4dab-ae92-0e0acb6fc36a

📥 Commits

Reviewing files that changed from the base of the PR and between 73bf521 and b775291.

📒 Files selected for processing (1)

• src/Dockerfile