Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Click Next and proceed to Create Certificate

  2. Wait for the certificate to be created. Copy the certificate’s ocid and set it to oci.certificates.id property in helm chart value file

TLS Backendset Secret

The SSL configuration between the load balancer and the backend servers (worker nodes) in the backend set is known as backend SSL. In this case, the backend set is refering to Platform Pod. To implement backend SSL, you associate an SSL certificate in the form of Kubernetes secret with the load balancer's backend set.

We already have server certificate, CA certificate and private key generated from the previous section. These certificates and private key can be reuse to generate the kubernetes secret needed by the backend set.

To store the certificate and the key as a secret in Kubernetes

Code Block
kubectl create secret generic ca-ser-secret -n uepe --from-file=tls.crt=tls.crt --from-file=tls.key=tls.key --from-file=ca.crt=ca.crt

Now, the backend set secret named ca-ser-secret has been created in the namespace uepe.

Info

The secret name ca-ser-secret should’t be changed as it is used internally in PE helm chart

Install Helm Chart

Although the number of helm value combinations to set is virtually endless, some values should more or less always be set.

...