The following settings are used for TLS certificates.
wallaroo.example.com
, then the Subject CNs would be wallaroo.example.com
..crt
) and TLS private key (.key
). Store these in a secure location - these will be installed into Wallaroo at a later step.The following is for updating SSL certificates in Wallaroo for a Kots based installation.
Access the Kots Administrative Dashboard in your browser. This can be done either after installation, or through the following command (assuming your Wallaroo instance was installed into the namespace wallaroo
or kotsadm
for Single Node installations). By default this provides the Kots Administrative Dashboard through the URL https://localhost:8800
.
kubectl kots admin-console --namespace wallaroo
From the Wallaroo Dashboard, select Config and set the following:
TLS Certificates
Once complete, scroll to the bottom of the Config page and select Save config.
A pop-up window will display The config for Wallaroo Enterprise has been updated.. Select Go to updated version to continue.
From the Version History page, select Deploy. Once the new deployment is finished, you will be able to access your Wallaroo services via their DNS addresses.
SSL certificates for Helm based installations of Wallaroo are stored as Kubernetes secrets. SSL certificates are set during the Wallaroo install procedure. The following procedure defines how to update the secret key with new TLS certificates.
Before start, set the Kubernetes default namespace to match the ones used for Wallaroo. For example, if Wallaroo is installed in the wallaroo
namespace, that command is:
kubectl config set-context --current --namespace wallaroo
Before starting, delete the old kubectl secret used to store the security certificates. This was set during the initial Wallaroo installation via helm and saved as the helm
value custTlsSecretName
.
To delete the old Wallaroo kubectl secret This is done with the kubectl delete secret
command. For example, if the Wallaroo secret is stored as cust-cert-secret
, use the following command:
kubectl delete secret cust-cert-secret
The following creates a new Kubectl secret from the SSL certificates. This should use the same name as the Wallaroo kubectl secret that was just deleted.
This is done with the command kubectl create secret tls
command with the following items:
helm
settings for custTlsSecretName
.For example, if the following settings are used:
example.com.crt
example.com.key
cust-cert-secret
Then the kubectl secret create command is:
kubectl create secret tls cust-cert-secret --cert=example.com.crt --key=example.com.key --namespace wallaroo
helm
based installation of Wallaroo with the following command to use the new kubectl secret key and certificates:kubectl rollout restart deployment api-lb
This will reset the api-lb
service and the procedure is complete.