...

• Convert the password in the application-dbs.yml file to Base64 format.
  Example command for Windows Powershell: [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("changeme"))
  Example command for Linux: echo -n "changeme" | base64 -w0
  Both example commands lead to the output Y2hhbmdlbWU=.

• Create a yuuvis-secrets.yml file with the following content:
  

  Code Block
  apiVersion: v1 kind: Secret metadata: name: yuuvis-secrets namespace: yuuvis type: Opaque data: POSTGRES_PASSWORD: Y2hhbmdlbWU=

  The section data contains a list of key-value pairs that can contain multiple entries. As spacers within the string key name, only underscores are allowed. The value is the password in Base64 format.

• Create a Kubernetes Secret by running the command kubectl apply -f yuuvis-secrets.yml.

• Replace the password in the application-dbs.yml file by a placeholder:
  

  Code Block
  yuuvis.db.password: ${POSTGRES_PASSWORD}

  
  

• Adjust the deployments of all yuuvis® services using the profile dbs by extending the section env:
  

  Code Block
  env: - name: POSTGRE_PASSWORD valueFrom: secretKeyRef: name: yuuvis-secrets key: POSTGRE_PASSWORD

  The name and the key given in secretKeyRef have to correspond to the name and the data value defined in the file yuuvis-secrets.yml.

Summary

Profiles act as globally reusable configuration elements or allow for the customization of specific service instances. The file name defines whether the configured parameters are available to multiple services or only one specific service. The profiles can be modified directly before the deployment or in a running system. Custom profiles can be added and referenced as well in addition to the always installed profiles. Sensitive data like passwords can be outsourced from the profiles and stored in Kubernetes Secrets instead.

...

...