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
aws-node v1.14.0+ supports NetworkPolicy enforcement according to changelog. I'd love to be able to control enabling this or not via the eksctl configuration.
I understand that eksctl clusters provide aws-node aka. vpc-cni as a self-managed addon, not listed under addons in the eksctl configuration file, and should therefor follow documentation about enabling it for self-managed addon. I've so far tried and failed, and I'm not sure what goes on - but thats a separate topic to being allowed to enable it via .
Overall though, it would be great to be able to enable NetworkPolicy enforcement directly through the eksctl cluster configuration and not require manual kubectl patches, especially since these will would get replaced if we would use eksctl utils update-aws-node later at some point in time.
The text was updated successfully, but these errors were encountered:
aws-node
v1.14.0+ supports NetworkPolicy enforcement according to changelog. I'd love to be able to control enabling this or not via theeksctl
configuration.There is a documented way to enable this both for being a managed addon and for self-managed addons.
I understand that
eksctl
clusters provideaws-node
aka.vpc-cni
as a self-managed addon, not listed underaddons
in theeksctl
configuration file, and should therefor follow documentation about enabling it for self-managed addon. I've so far tried and failed, and I'm not sure what goes on - but thats a separate topic to being allowed to enable it via .Overall though, it would be great to be able to enable NetworkPolicy enforcement directly through the eksctl cluster configuration and not require manual
kubectl
patches, especially since these will would get replaced if we would useeksctl utils update-aws-node
later at some point in time.The text was updated successfully, but these errors were encountered: