Openstack-Cloud-Controller-Manager doesn't use the cluster-name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CDK Addons |
In Progress
|
Undecided
|
Adam Dyess | ||
Openstack Cloud Controller Charm |
In Progress
|
Undecided
|
Adam Dyess |
Bug Description
As demonstrated in https:/
Args:
/
-
--v=1
-
-
-
-
-
set the cluster-name twice -- which ends up using the environment set name instead since it comes second in the argument list.
The DaemonSet default value for cluster-name is `kubernetes` -- meaning that if you were to use two or more clusters attached to the same openstack cloud project, all the resources intended to be unique for your cluster would clash with the second cluster.
for example:
A loadbalancer for the hello service in the default domain might be named kube_service_
Both clusters would attempt to use this same load-balancer for the different services each named hello
tags: | added: sts |
Affects
* cdk-addons 1.28
* cdk-addons 1.27
* cdk-addons 1.26
Does not affect cdk-addons 1.25 or Prior