Add extra security context capability for proxy init container

[mattbates]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @mattbates, 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 refines the security context configuration for the proxy init container. The primary goal is to ensure the container possesses all necessary capabilities to correctly apply network rules, specifically those managed by nftables, by granting additional network permissions and explicitly confirming its root execution context.

Highlights

• Security Context Capabilities: I've updated the proxy init container's security context to include the NET_RAW capability alongside NET_ADMIN. This is explicitly noted as being required for applying nftables rules.
• Explicit Root Execution: I've added an explicit RunAsNonRoot: ptr.To(false) setting to the proxy init container's security context. While RunAsUser: ptr.To(int64(0)) already implies running as root, this addition makes the intent clearer and potentially more robust against certain security policies.

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 the NET_RAW capability and explicitly sets RunAsNonRoot: false for the Envoy proxy's init container. These changes enhance the security context to ensure nftables rules can be applied correctly and robustly across different Kubernetes environments. The changes are reasonable and well-justified. I have one minor suggestion to improve code style consistency.

[gemini-code-assist]

This blank line appears to be unnecessary and is inconsistent with the coding style elsewhere in the repository. For example, other struct literals in internal/helper/config.go do not have blank lines before the closing brace.

Please remove it to maintain a consistent coding style.