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

Support for setting init container options and per-pod security groups #631

Merged
merged 5 commits into from
Nov 9, 2021

Conversation

viveklak
Copy link
Contributor

@viveklak viveklak commented Nov 9, 2021

Proposed changes

  • Add support for setting the init container image.
  • Add support for setting DISABLE_TCP_EARLY_DEMUX.

Builds on top of #617 which seems to be failing on schema validation due to command dispatch workflow (only relevant for external contributions). This adds a test on top of #617 but is otherwise identical.

Related issues (optional)

Fixes #619
Fixes #620

h/t @alex-hunt-materialize

Relates to, but doesn't solve: #622

Supports setting the init container image and DISABLE_TCP_EARLY_DEMUX
env var.

This allows users to upgrade their version of the CNI, and to support
per-pod security groups.
add custom images to cluster example, and reduce line length in
disableTcpEarlyDemux description.
@github-actions
Copy link

github-actions bot commented Nov 9, 2021

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@viveklak viveklak changed the title Vl/init container support Support for setting init container options and per-pod security groups Nov 9, 2021
@github-actions
Copy link

github-actions bot commented Nov 9, 2021

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@@ -50,6 +52,7 @@ function computeVpcCniYaml(cniYamlText: string, args: VpcCniInputs): string {
// Rewrite the envvars for the CNI daemon set as per the inputs.
const daemonSet = cniYaml.filter(o => o.kind === "DaemonSet")[0];
const env = daemonSet.spec.template.spec.containers[0].env;
const initEnv = daemonSet.spec.template.spec.initContainers[0].env;
Copy link
Member

Choose a reason for hiding this comment

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

Are we guaranteed to have at least one initContainer?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes - as per nodejs/eks/cni/aws-k8s-cni.yaml

@viveklak viveklak merged commit 0ac1e0c into master Nov 9, 2021
@pulumi-bot pulumi-bot deleted the vl/init_container_support branch November 9, 2021 20:30
flostadler pushed a commit that referenced this pull request Sep 4, 2024
Support for setting init container options and per-pod security groups
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants