Add support for specifying env vars for the Karmada operator

[jabellard]

What type of PR is this?

/kind feature

What this PR does / why we need it:
This PR adds support for injecting arbitrary environment variables into the Karmada Operator deployment.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada operator Helm chart`: It's now possible to set environment variables for the Karmada operator deployment.

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign a7i for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• charts/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @jabellard, 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!

I've added a new feature to the Karmada operator Helm chart that enables users to inject arbitrary environment variables into the Karmada Operator deployment. This enhancement provides greater flexibility for configuring the operator, such as setting up proxy settings or other operational parameters, directly through the Helm chart values.

Highlights

• Helm Chart Configuration: Introduced a new configuration option (operator.env) in the values.yaml file for the Karmada operator Helm chart, allowing users to specify environment variables for the operator's deployment.
• Deployment Customization: Modified the karmada-operator-deployment.yaml template to conditionally include an env block, which will populate environment variables based on the operator.env values provided in the Helm chart.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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 adds support for specifying environment variables for the Karmada operator via its Helm chart. The changes are well-implemented, with clear documentation and examples in values.yaml. My review includes one suggestion for the deployment template to align with common Helm templating practices for improved maintainability.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.33%. Comparing base (b8f6874) to head (dbc513a).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6596      +/-   ##
==========================================
- Coverage   45.34%   45.33%   -0.01%     
==========================================
  Files         687      687              
  Lines       56393    56393              
==========================================
- Hits        25571    25566       -5     
- Misses      29226    29229       +3     
- Partials     1596     1598       +2     

Flag	Coverage Δ
unittests	45.33% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jabellard]

/retest