Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

In production environments it is recommended to store any secret data in Kubernets secrets. The Smartfacts and OSLC Adapter charts support the use of pre-installed Kubernetes secrets.

default secret name

name of property to override default secret name

secret data property name

secret data property meaning

TLS certificates for ingresses

smartfacts-certs

global.cert.crtFullChain

tls.crt

global.cert.key

tls.key

Username and Password of the Administration user in Keycloak

smartfacts-keycloak-admin-secret

KEYCLOAK_PASSWORD

KEYCLOAK_USER

Data for connecting to the OIDC provider

smartfacts-oidc-secrets

global.secrets.oidcSecretName

campId

ID of camp client in OIDC issuer

camSecret

Secret of camp client in OIDC issuer

smartfactsId

ID of smartfacts client in OIDC issuer

smartfactsSecret

Secret of smartfacts client in OIDC issuer

Username and password of the postgresql database used for Keycloak

smartfacts-postgresql

password

postgres-password

The Java truststore used by the Smartfacts platform and genoslc toolservice

smartfacts-truststore

server.key

truststore.jks

ca.crt

ca.key

certtool.log

head.crt

server.crt

server.jks

smartfacts-truststore-password

password

regcred

.dockerconfigjson

smartfacts-mongodb-connection-secret

connection-string

smartfacts-oauth10a-encryption-key-secret

ENCRYPTION_KEY

smartfacts-oslc-technical-user-secret

env.tool.adaptedToolTechnicalUserAuthorizationHeader

adaptedToolTechnicalUserAuthorizationHeader

  • No labels