Daemonset pods still get IPs from primary subnets

[neilharris123]

I enabled custom networking in my cluster so that my pods would receive IP addresses from some secondary subnets I added from a secondary VPC CIDR.
This worked for most pods (adn deployment and statefulsets), however, I noticed that daemonset pods were still assigned IP addresses from the primary subnets where the node gets its IP address from.

I recycled all nodes, and this is still the case.

Is this expected behaviour, or have I missed something?

Environment:

• Kubernetes version: 1.29
• CNI Version: v1.18.5-eksbuild.1

[orsenthil]

Do you see any errors in plugin.log or ipamd.log ?

I noticed that daemonset pods were still assigned IP addresses from the primary subnets where the node gets its IP address from.

Are they hostNetworking pods by any chance?

Custom networking ip assignment should not depend on the kind of the resource (Deployment or Daemonset).

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

[github-actions]

Issue closed due to inactivity.