ArgoCDAddon Pods failing with does not have label vpc.amazonaws.com/PrivateIPv4Address

[larskinder]

Hi,

I have encountered issues with the ArgoCDAddon, when trying to deploy it with the default settings.

const addOns: Array<blueprints.ClusterAddOn> = [
      new blueprints.addons.AwsLoadBalancerControllerAddOn(),
      new blueprints.addons.ExternalDnsAddOn({hostedZoneResources: ["HostedZone"]}),
      new blueprints.addons.NginxAddOn({
        internetFacing: true,
        backendProtocol: "tcp",
        externalDnsHostname: subDomain,
        crossZoneEnabled: false
      }),
      new blueprints.addons.ArgoCDAddOn(), // Pods fail on deployment with "does not have label vpc.amazonaws.com/PrivateIPv4Address"
      new blueprints.VpcCniAddOn({
        version: 'v1.18.3-eksbuild.1',
        enableWindowsIpam: true
      }),
      new WindowsVpcCni(), // does not work. Need to apply config map manually in charts/cluster-config
      new blueprints.addons.CoreDnsAddOn(),
      new blueprints.addons.KubeProxyAddOn(),
      new blueprints.addons.MetricsServerAddOn(),
      new blueprints.addons.KarpenterAddOn(),
    ];

When validating the documentation, it does not seem like you need changes in the vpc cni config map, but when the default pods for argocd try to start, they fail with
does not have label vpc.amazonaws.com/PrivateIPv4Address

I have noticed this issue in the past for Windows pods, that require updating the amazon-vpc-cni in kube-system.

To me it seems like something is missing in the documentation that is crucial for Argo pods.

Would be great to get feedback and in case it is a known issue, add this to the documentation.

Links

https://aws-quickstart.github.io/cdk-eks-blueprints/addons/argo-cd/

[github-actions]

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days