Senthil Kumaran

Hi @matt-snider , both these suggestions worked. I think, applying the patch to your repo will be good idea. --- Non interactive migrate failed for me at 85th task. It...

> I'm happy to open a PR for this change. @kwohlfahrt ; sure, please share your change.

Custom Networking is a separate feature over the _solution_ for IP-exhausion with `ENABLE_SUBNET_DISCOVERY` As we mention in our blog post - https://aws.amazon.com/blogs/containers/amazon-vpc-cni-introduces-enhanced-subnet-discovery/ Custom networking takes precedence when both features are...

> Any news regarding AWS internal decision? No news yet. this is desirable feature that we will bring it up for prioritization.

@haouc - I pointed out to the GitVersion that is displayed during the bootstrap ( https://github.com/aws/amazon-vpc-resource-controller-k8s/blob/964a3cce8281e25c185369f63859ed63bedd491f/main.go#L179) . this is different from that log; the request is if the controller version...

I have updated the userAgent to reflect the vpc-resource-controller and gitVersion in this PR https://github.com/aws/amazon-vpc-resource-controller-k8s/pull/455

The code changes look good to me.

We don't have an equivalent of GlobalNetworkPolicy in VPC CNI network policy implementation. The policies should be namespace scoped.

The equivalent "GlobalNetworkPolicy" will come through AdminNetworkPolicy - https://github.com/aws/containers-roadmap/issues/2243 - which will satisfy Deny traffic at a cluster level / Allow traffic at Cluster Level use cases - which is...

@yash97 - Did the dependency update bring the API change? Why do we have to change the event handler interfaces.