Closed michal-gubricky closed 3 months ago
What this PR does / why we need it: This PR sets the cluster name in the OCCM to make the name for the ingress-nginx load balancer unique
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes https://github.com/SovereignCloudStack/k8s-cluster-api-provider/issues/495
fixes #<issue number>(, fixes #<issue_number>, ...)
Tested with the cluster name set to cs-cluster:
cs-cluster
k describe po openstack-cloud-controller-manager-9l724 -n kube-system --kubeconfig cs-cluster.kubeconfig Containers: openstack-cloud-controller-manager: Environment: CLOUD_CONFIG: /etc/config/cloud.conf CLUSTER_NAME: cs-cluster
After the installation of Ingress-NGINX, the load balancer was created in the gx-scs with the expected name, see attached pic.
gx-scs
What this PR does / why we need it: This PR sets the cluster name in the OCCM to make the name for the ingress-nginx load balancer unique
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes https://github.com/SovereignCloudStack/k8s-cluster-api-provider/issues/495Tested with the cluster name set to
cs-cluster
:After the installation of Ingress-NGINX, the load balancer was created in the
gx-scs
with the expected name, see attached pic.