Auto-restart deployments on config map changes

[sd109]

See https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments

[gemini-code-assist]

Summary of Changes

Hello @sd109, 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 significantly enhances the operational robustness of several Helm charts by introducing automated deployment restarts. By embedding checksums of relevant ConfigMaps directly into the pod templates, the system now ensures that any configuration changes are seamlessly applied through a rolling update, eliminating the need for manual intervention. This improvement streamlines the deployment process and reduces potential downtime associated with configuration updates for the cofide-agent, cofide-connect-ui, cofide-connect, and cofide-observer services.

Highlights

• Automated Deployment Restarts: Implemented a mechanism to automatically restart deployments when their associated ConfigMaps are updated for the cofide-agent, cofide-connect-ui, cofide-connect, and cofide-observer Helm charts.
• Checksum Annotations: Utilized checksum/config and checksum/envoy-config annotations in the pod metadata to track changes in configmap.yaml and configmap-envoy.yaml respectively, ensuring Kubernetes triggers a rolling update upon modification.
• Targeted ConfigMap Monitoring: The cofide-agent, cofide-connect, and cofide-observer charts now monitor configmap.yaml for changes, while cofide-connect-ui and cofide-connect also monitor configmap-envoy.yaml.
• Minor Formatting Fix: A small whitespace issue was corrected in the containerPort definition within the cofide-connect deployment template.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 implements a common Helm pattern to automatically trigger a rolling update for deployments when their associated ConfigMaps change. The implementation is sound across most of the charts. However, I've identified a potential issue in the cofide-agent deployment where the checksum includes a stateful ConfigMap. This could lead to unintended redeployments. I've provided a suggestion to make the checksum more specific and robust, targeting only the configuration values that affect the deployment.

[alec-w]

Missed in my review - a Chart patch version bump is required