You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 5c recommends setting the following env var on the VPC CNI daemonset:
ENI_CONFIG_LABEL_DEF=topology.kubernetes.io/zone
Step 5a recommends creating ENIConfigs manually via kubectl.
I was hoping to use the Helm chart in this repo to install the ENIConfigs, and otherwise manage upgrades to the VPC CNI add on. However, by default the Helm chart names ENIConfig using the format REGION + USER-SUPPLIED-NAME. But EKS doesn't put any label on nodes by default that matches this format.
Is this intentional? It feels a little like the Helm chart should produce names that work well with ENI_CONFIG_LABEL_DEF (etc) out-of-the-box?
Environment:
Kubernetes version (use kubectl version): 1.21
CNI Version: v1.9.0 (Helm chart 1.1.8)
OS (e.g: cat /etc/os-release): not relevant
Kernel (e.g. uname -a): not relevant
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
What happened:
I've been following the CNI custom networking instructions in the EKS docs.
Step 5c recommends setting the following env var on the VPC CNI daemonset:
Step 5a recommends creating ENIConfigs manually via
kubectl
.I was hoping to use the Helm chart in this repo to install the ENIConfigs, and otherwise manage upgrades to the VPC CNI add on. However, by default the Helm chart names ENIConfig using the format
REGION
+USER-SUPPLIED-NAME
. But EKS doesn't put any label on nodes by default that matches this format.Is this intentional? It feels a little like the Helm chart should produce names that work well with
ENI_CONFIG_LABEL_DEF
(etc) out-of-the-box?Environment:
kubectl version
): 1.21cat /etc/os-release
): not relevantuname -a
): not relevantThe text was updated successfully, but these errors were encountered: