Currently, the ccm will automatically apply metadata to nodes with topology.kubernetes.io/zone and topology.kubernetes.io/region set to the same value.
However, this will cause compatibility issue with rook-ceph. The gist is that ceph requires all topology meta data be unique (i.e., zone != region).
May I suggest to allow users to custom the topology.kubernetes.io/region metadata in the configure file such as:
[Global]
api-url = <CloudStack API URL>
api-key = <CloudStack API Key>
secret-key = <CloudStack API Secret>
project-id = <CloudStack Project UUID (optional)>
zone = <CloudStack Zone Name (optional)>
region = <Region Name (optional)>
ssl-no-verify = <Disable SSL certificate validation: true or false (optional)>
Currently, the ccm will automatically apply metadata to nodes with
topology.kubernetes.io/zoneandtopology.kubernetes.io/regionset to the same value.However, this will cause compatibility issue with rook-ceph. The gist is that ceph requires all topology meta data be unique (i.e., zone != region).
May I suggest to allow users to custom the
topology.kubernetes.io/regionmetadata in the configure file such as: