Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

Using GV-Essentials chart

...

You can configure a custom TLS certificates during gv-essentials chart installation.

...

Info

If you don’t want to import a custom certificate leave Use Custom TLS Certificate disabled, a self-signed certificate will then be auto generated instead.

Option 2 - Using kubectl (manual method)

Have your private key and certificate in the PEM format (e.g. openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem) and create a file called custom_cert.yaml anywhere inside the cluster with the following content:

Code Block
apiVersion: v1
kind: Secret
metadata:
  name: custom-default-cert
  namespace: kube-system
type: kubernetes.io/tls
data:
  tls.crt: $CERTIFICATE_BASE64
  tls.key: $PRIVATE_KEY_BASE64
---
apiVersion: traefik.containo.us/v1alpha1
kind: TLSStore
metadata:
  name: default
  namespace: kube-system
spec:
  defaultCertificate:
    secretName: custom-default-cert

...

Replace $CERTIFICATE_BASE64 with the base64 encoded content of your certificate (e.g. cat certificate.pem | base64)

...

.

...

...

Run kubectl apply -f custom_cert.yaml

Sources

...

...