Skip to content

Commit

Permalink
Update README for DISABLE_TCP_EARLY_DEMUX
Browse files Browse the repository at this point in the history
  • Loading branch information
SaranBalaji90 authored and jayanthvn committed Oct 30, 2020
1 parent a8bea42 commit 68e39f2
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -432,10 +432,10 @@ Type: Boolean as a String

Default: `false`

If `ENABLE_POD_ENI` is set to `true`, in order for the kubelet on the node to connect via TCP to pods that are using
per pod security groups, `DISABLE_TCP_EARLY_DEMUX` should be set to `true`. This will increase the local TCP connection
latency slightly, that is why it is not on by default. Details on why this is needed can be found in
this [#1212 comment](https://github.com/aws/amazon-vpc-cni-k8s/pull/1212#issuecomment-693540666).
If `ENABLE_POD_ENI` is set to `true`, in order for the kubelet to connect via TCP (for liveness or readiness probes)
to pods that are using per pod security groups, `DISABLE_TCP_EARLY_DEMUX` should be set to `true` for `amazon-k8s-cni-init`
container under `initcontainers`. This will increase the local TCP connection latency slightly.
Details on why this is needed can be found in this [#1212 comment](https://github.com/aws/amazon-vpc-cni-k8s/pull/1212#issuecomment-693540666).
To use this setting, a Linux kernel version of at least 4.6 is needed on the worker node.

### ENI tags related to Allocation
Expand Down

0 comments on commit 68e39f2

Please sign in to comment.