search

Azure / AKS

Azure Kubernetes Service
https://azure.github.io/AKS/
1.95k stars 305 forks source link

[Feature Request] Pod Static IP #2189

Open palma21 opened 3 years ago

palma21 commented 3 years ago

Use a specific IP address for a pod.

yuzsun commented 2 years ago

any update on this feature? does Azure CNI support for reserving pod ip address now?

aanandr commented 2 years ago

@yuzsun - this ask is under investigation now and we dont have an clear dates yet. Are you looking for static IP both for ingress and egress connections? Is there a preference (priority) for one of them?

derek-burdick commented 2 years ago

If you consider the use case for Cassandra. When using Azure CNI, i would like to deploy an IP address, and assign it to the POD on startup.

Ideally a statefulset when scaled up and down will use the same IP address per pod. While technically complicated, perhaps could be stored or specified in the statefulset metadata?

aanandr commented 2 years ago

Thanks @derek-burdick. We are prioritizing static IP for egress connections higher than for ingress connections. Why doesnt cluster service serve the purpose for you?

kitforbes commented 9 months ago

I have a use case where I'd like to set the pod's IP for egress.

We connect to our partner through Azure's Virtual Network Gateway, and they only accept communication from a known private IP address from our pre-defined subnet. Has there been any movement since February '22?

Edit: Just noticed the Project link and can see that this is still on the backlog.

easy1481437320 commented 2 months ago

any update on this feature? does Azure CNI support for reserving pod ip address now?

JeanRessouche commented 1 month ago

I have a use case where I'd like to set the pod's IP for egress.

We connect to our partner through Azure's Virtual Network Gateway, and they only accept communication from a known private IP address from our pre-defined subnet. Has there been any movement since February '22?

Edit: Just noticed the Project link and can see that this is still on the backlog.

exact same scenario here, digging for a solution. using an internal loadbalancer allow us to select the subnet used for inbound traffic but not four outbound