What is the replacement for the deprecated loadBalancerIP attribute in Services

Viewed 44
1 Answers

Here is the discussion on the k8s github about what's going to happen to that field [1]

My understanding from reading the conversation and the documentation you pointed out is that there is a consensus that the field needs to go away because it doesn't support dual-stack. But for now and until cloud providers have an alternative (via annotation) to setting a static LB IP. That field will remain and will continue to work.

We (GCP) don't have that alternative yet. So for now you continue using that field until we have it implemented. In any case it will be mentioned in the GKE release notes

[1] https://github.com/kubernetes/enhancements/pull/1992

Related