...
| Expand |
|---|
| title | Example - Secret object |
|---|
|
| Code Block |
|---|
kubectl create secret generic authorization-server-secrets --namespace <namespace> \
--from-literal=managementApiUsername=<username> \
--from-literal=managementApiPassword=<password> \
--from-file=jwtKeystore=<keystore file path encoded in Base64 format> \
--from-literal=jwtKeyId=<id> \
--from-literal=jwtKeyPassword=<password> \
--from-literal=jwtKeystorePassword=<password> |
|
Keystore file can be encoded in Base64 format with the following command:
| Code Block |
|---|
base64 -i <keystore file path> -o <B64 keystore file name>.txt |
Helm Values
| Expand |
|---|
| title | Example - Helm installation with existing kubernetes secret |
|---|
|
| Code Block |
|---|
helm upgrade <installation name> --install ue-internal/usage-engine-private-edition --version <helm chart version> --set "global.imagePullSecrets[0].name=ecrcred" \
--set persistence.enabled=true \
--set environment=docker-desktop \
--set operator.installCRDs=false \
--set authorizationServer.enabled=true |
|
...
| Code Block |
|---|
kubectl get secrets/authorization-server-secrets -n default --template={{.data.managementApiPassword}} | base64 -d |
If authorization-server-secrets exists, its secret value will be used.
If --set is executed from the helm command, then helm set value will overwrite the existing secret if there is any.
If both secret and helm values are not exist, fail the installation.