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
It has pem format which has many lines and /n. The automation has difficulty to replace certficate-authority strings for different clusters.
Do you support base64 encode string for this certificate-authority? like
# Clusters list for CLI configuration
clusters:
- name: test1
server: https://****:6443
certificate-authority: |
<base64 encoded string>
insecure-skip-tls-verify: false
# Alternative context name for this cluster
contextName: test
or any workaround would be much appreciated.
Thank you
Henry
The text was updated successfully, but these errors were encountered:
I am in the same situation, for work around, I use yq to manipulate the content of ca, e.g. yq -i e '.config.clusters[0].certificate-authority = "'"$(sudo cat /var/lib/rancher/k3s/server/tls/server-ca.crt)"'"' /vagrant/HelmWorkShop/loginapp/values.yaml
We are automating deploy loginapp + dex. We have difficulty on replace cluster certificate-authority strings.
It has pem format which has many lines and /n. The automation has difficulty to replace certficate-authority strings for different clusters.
Do you support base64 encode string for this certificate-authority? like
or any workaround would be much appreciated.
Thank you
Henry
The text was updated successfully, but these errors were encountered: