user-defined loadbalancer-ip for a kubernetes service is not being used
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Vedamurthy Joshi |
Bug Description
R4.0 3028
Per, https:/
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": [
{
}
],
"type": "LoadBalancer",
}
}
[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]#
tags: | added: contrail-kube-manager |
Fix checked in today. Pls verify in next build.