user-defined loadbalancer-ip for a kubernetes service is not being used

[Vedamurthy Joshi]

R4.0 3028

Per, https://kubernetes.io/docs/user-guide/services/#type-loadbalancer , one could define the loadBalancerIP himself.
But it is not being configured.

Below, user supplied 30.1.1.200 as the public ip, but it configured 30.1.1.3

[root@vedu-vm1-1 centos]# cat httpservice.yaml
{
    "kind": "Service",
    "apiVersion": "v1",
    "metadata": {
        "name": "frontend-service1"
    },
    "spec": {
        "selector": {
            "app": "nginx",
            "role": "frontend"
        },
        "ports": [
            {
                "name": "http",
                "protocol": "TCP",
                "port": 82,
                "targetPort": 80
            }
        ],
        "type": "LoadBalancer",
        "loadBalancerIP": "30.1.1.200"
    }
}

[root@vedu-vm1-1 centos]# kubectl get service
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
frontend-service1 10.107.205.21 ,30.1.1.3 82:30318/TCP 4m <<<
kubernetes 10.96.0.1 <none> 443/TCP 4d
[root@vedu-vm1-1 centos]#

[Sachchidanand Vaidya (vaidyasd)]

Fix checked in today. Pls verify in next build.