You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloudstack then randomly allocated a public ip as external ip
❯ kubectl get svc nginx-deployment
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
nginx-deployment LoadBalancer 10.109.88.98 10.0.54.83 80:32739/TCP 4m24s
Suppose a user wants a specific public ip as a loadbalancer ip
Currently it's not possible even if we manually edit the service.yaml, cloudstack again allocates a random public ip
If it helps you just need to associate an IP with the network in which your Kubernetes cluster is running before exposing your service and it should work.
cmk associate ipaddress ipaddress=10.1.1.218 networkid=${kubernetes_network_id}# or via GUI
kubectl expose deploy/nginx-deployment --port=80 --type=LoadBalancer --load-balancer-ip="10.1.1.218"
ISSUE TYPE
COMPONENT NAME
Component: Kubernetes/Networking
CLOUDSTACK VERSION
Cloudstack 4.18
SUMMARY
Support static public ip address as a Load balancer IP
STEPS TO REPRODUCE
Deploy Kubernetes cluster on Cloudstack
Create a deployment for example a nginx deployment
kubectl expose deploy/nginx-deployment --port=80 --type=LoadBalancer
Currently it's not possible even if we manually edit the service.yaml, cloudstack again allocates a random public ip
EXPECTED RESULTS
Cloudstack should allocate the specified public ip address
ACTUAL RESULTS
Clodudstack is allocating a radom public ip address
The text was updated successfully, but these errors were encountered: