Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add ability to the helm chart to specify initContainers. #7668

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

danielricart
Copy link

Fixes #N/A

Description
Currently, the helm chart does not support adding initContainers to the deployment for things like ensuring that IAM credentials are valid.

This PR aims to add support for users in specifying initContainers in the Values file.

The implementation follows the practices applied in other similar fields that are already present.

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened:
  • No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Currently, the current helm chart does not support adding initContainers to the deployment for things like ensuring that IAM credentials are valid.

This PR aims to support users to especify initContainers in the Values file.

The implementation follows the practices applied in other similar fields that are already present.
@danielricart danielricart requested a review from a team as a code owner January 31, 2025 15:57
@danielricart danielricart requested a review from engedaam January 31, 2025 15:57
Copy link

netlify bot commented Jan 31, 2025

Deploy Preview for karpenter-docs-prod canceled.

Name Link
🔨 Latest commit 2d3082b
🔍 Latest deploy log https://app.netlify.com/sites/karpenter-docs-prod/deploys/67a2031419f8030008b47960

@@ -68,6 +68,11 @@ dnsConfig: {}
# options:
# - name: ndots
# value: "1"
# -- add additional initContainers to run before karpenter container starts
initContainers: {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an interesting use-case. Why can't you just ensure that your permissions are correct (and/or) see the failure once Karpenter starts OR rely on something like #7624 to ensure this

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validating IAM Credentials is one common use of initContainers and the one we want to check (and for which #7624 may help), but initContainers can also be used for other use cases specific to each cluster maintainer's needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants