Skip to content

Latest commit

 

History

History
73 lines (56 loc) · 1.42 KB

secrets.md

File metadata and controls

73 lines (56 loc) · 1.42 KB
Raw

Secrets

Secret values are obfuscated by applying base64 encoding.

Create Secrets

Create with oc Tool

Create key/value pair secrets:

oc create secret generic db-secrets \
  --from-literal DB_USERNAME=db-user \
  --from-literal DB_PASSWORD=asdf1234

Check created secret resource:

$ oc get secret db-secrets -o yaml
apiVersion: v1
data:
  DB_PASSWORD: YXNkZjEyMzQ=
  DB_USERNAME: ZGItdXNlcg==
kind: Secret
metadata:
  name: db-secrets
type: Opaque

Create by resource-yaml / template

Use stringData section to let Openshift make the base64 conversion.

apiVersion: v1
kind: Secret
metadata:
  name: test-secret
type: Opaque
data:
  username: dmFsdWUtMQ0K
  password: dmFsdWUtMg0KDQo=
stringData:
  hostname: myapp.mydomain.com

Create: oc apply -f filename.yaml

resulting secret

apiVersion: v1
data:
  hostname: bXlhcHAubXlkb21haW4uY29t
  password: dmFsdWUtMg0KDQo=
  username: dmFsdWUtMQ0K
kind: Secret
metadata:
  name: test-secret
type: Opaque

username and password are unchanged from the input yaml. The hostname is moved to the data section and the value is base64.

Create from file

Secrets from file are also supported. They have to be mounted similar to the file based configmaps.

oc create secret generic webdav-users --from-file .htdigest=webdav.htdigest
oc set volume dc/website --add --secret-name webdav-users --mount-path=/opt/app-root/secrets/webdav