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.

Sign up for GitHub

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

Jump to bottom

Support setting DISABLE_TCP_EARLY_DEMUX on init container #620

Closed
alex-hunt-materialize opened this issue Sep 7, 2021 · 0 comments · Fixed by #617 or #631
Closed

Support setting DISABLE_TCP_EARLY_DEMUX on init container #620

alex-hunt-materialize opened this issue Sep 7, 2021 · 0 comments · Fixed by #617 or #631
Assignees
@alex-hunt-materialize
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@alex-hunt-materialize
Copy link
Contributor

Affected area

There is currently no way to set DISABLE_TCP_EARLY_DEMUX on the init container. This is required for probes to reach containers from the kubelet when using per-pod security groups.

Please add an additional argument to configure this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alex-hunt-materialize alex-hunt-materialize

Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Milestone
No milestone
2 participants
@pulumi-bot @alex-hunt-materialize