[WIP] Support AWS with token exchange sidecar injection

[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 lays the groundwork for integrating AWS token exchange into the sidecar injection mechanism. The primary functional change involves adding a new annotation to facilitate AWS IAM role specification, complemented by a significant refresh of the project's Go module dependencies to align with newer versions of Kubernetes and other core libraries.

Highlights

• AWS Integration: I've introduced a new Kubernetes pod annotation, spiffe.cofide.io/aws-role-arn, to enable the specification of AWS IAM Role ARNs. This is a foundational step towards supporting AWS token exchange for sidecar injection.
• Dependency Updates: I've performed a comprehensive update of Go module dependencies. This includes bumping versions for core Kubernetes libraries (API, client-go, apimachinery), various golang.org/x modules, OpenTelemetry, and other indirect dependencies, ensuring the project uses more recent and stable versions.

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 updates dependencies and adds a new constant for an AWS-specific annotation. I suggest separating dependency updates into a dedicated pull request and considering a more generic naming scheme for the new annotation.

[gemini-code-assist]

This pull request includes numerous dependency updates alongside the initial code for a new feature. It's generally better to handle dependency updates in a separate PR to simplify review and debugging.

[gemini-code-assist]

Consider a more generic naming convention for AWSRoleARNAnnotation to allow extensibility to other cloud providers in the future. For example, ProviderAnnotation and ProviderRoleAnnotation.