fix: fix release/0.17 vulnerabilities

[ridwanmsharif]

./ops/gmpctl.sh vulnfix

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the security posture of the release/0.17 branch by updating the base container images used across various critical components. The changes involve bumping the versions of distroless images for bash and libc, which are foundational to several services, thereby mitigating potential vulnerabilities and ensuring the system runs on more up-to-date and secure foundations.

Highlights

• Vulnerability Fixes: Updated base container images across multiple components to address identified vulnerabilities, ensuring the release/0.17 branch utilizes more secure dependencies.
• Image Tag Updates: The gke-distroless/bash image tag in charts/values.global.yaml and the gke-distroless/libc base image tags in several Dockerfiles were updated to newer versions.

Ignored Files

• Ignored by pattern: manifests/** (2)
  • manifests/operator.yaml
  • manifests/rule-evaluator.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

---

Old images, they held a flaw, New tags arrive, obeying law. Security's call, a swift update, To keep the code in a safer state.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates container image tags across several files to address vulnerabilities. The changes are straightforward version bumps. My review includes two suggestions to improve maintainability. First, I recommend quoting an image tag in charts/values.global.yaml to align with the file's stated convention. Second, I've pointed out that the base image version is duplicated across multiple Dockerfiles and suggested a refactoring to centralize this configuration, which will simplify future updates.