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
It seems that the "official" EKS tags applied automatically by EKS node-groups is eks:cluster-name and not CLUSTER_ID or Name.
Would you accept a PR to replace either or both of these values with eks:cluster-name?
If not, I believe that cni_metrics_helper is unusable with EKS managed nodegroups as they do not allow custom tags such as CLUSTER_ID or Name to be propagated to the EC2 instances.
The text was updated successfully, but these errors were encountered:
Any updates on this? We are considering using managed workers (EKS node groups) instead of unmanaged workers, but this makes the transition difficult if we don't want to give up CNI metrics.
There is also a chance that EKS allows us to propagate tags to instances in managed node groups in future, so it could also get "fixed" on that end. I think it would be cleaner if the cni-metrics-helper used the "standard" tags though, because then all you need to do is install the CNI plugin and cni metrics helper to an EKS cluster and it should "just" work.
It seems that the "official" EKS tags applied automatically by EKS node-groups is
eks:cluster-name
and notCLUSTER_ID
orName
.Would you accept a PR to replace either or both of these values with
eks:cluster-name
?If not, I believe that cni_metrics_helper is unusable with EKS managed nodegroups as they do not allow custom tags such as
CLUSTER_ID
orName
to be propagated to the EC2 instances.The text was updated successfully, but these errors were encountered: