The big disadvantage of this is that I can no longer use the set of the helm_release provider, otherwise pcc-xxx-ovh.com is split into several subkeys because of the .
As a result, I use a values file and this has another big drawback: I can no longer use the set_sentive for the username/password.
https://github.com/vsphere-tmm/helm-charts/blob/a210880c67c1738d96daf73c0926671885a994d5/charts/vsphere-csi/templates/secret.yaml#L24
When we set following helm values
the pod will try to connect to https://ovh instead of https://pcc-xxx-ovh.com
While this set up e works fine for vshpere-cpi.
As workaroud I renamed ovh as pcc-xxx-ovh.com to like
The big disadvantage of this is that I can no longer use the
set
of the helm_release provider, otherwisepcc-xxx-ovh.com
is split into several subkeys because of the.
As a result, I use a values file and this has another big drawback: I can no longer use theset_sentive
for the username/password.As i said above, it works fine with vsphere-cpi, to i can use set and set_sensitive
tf version: 1.6.0 vsphere-csi chart: 3.2.3