fix: set namespace from release namespace

[aagumin]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @aagumin, 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 refactors the Helm chart for the model-csi-driver to enhance its deployability and adherence to Helm best practices. The changes primarily focus on making resource naming and namespace assignment more dynamic, leveraging Helm's built-in variables and template functions. This ensures that chart resources are correctly scoped to the Helm release's namespace and have unique names, improving multi-tenancy support and deployment flexibility.

Highlights

• Dynamic Namespacing: All Kubernetes resources (ConfigMaps, ServiceAccount, DaemonSet) within the Helm chart now consistently use {{ .Release.Namespace }} for their namespace, ensuring they are deployed into the same namespace as the Helm release.
• Dynamic Resource Naming: ConfigMaps and the ServiceAccount now have their names dynamically generated using Helm template functions like include "model-csi-driver.fullname" . and include "model-csi-driver.serviceAccountName" ., preventing naming conflicts when multiple instances of the chart are deployed.
• ServiceAccount Configuration: A new serviceAccount section has been added to values.yaml, allowing users to conditionally create the ServiceAccount and specify a custom name for it, providing greater flexibility.

🧠 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 correctly refactors the Helm chart to use the release namespace instead of a hardcoded one, which is a great improvement for usability. The changes are consistent across all resources, and resource names are now dynamically generated based on the release name to prevent conflicts. I have one suggestion regarding a misleading filename that would improve the chart's maintainability.

[imeoer]

Thanks, LGTM!

[gaius-qi]

LGTM