Keycloak packaged by Bitnami

Keycloak is a high performance Java-based identity and access management solution. It lets developers add an authentication layer to their applications with minimum effort.

Overview of Keycloak

Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

helm install my-release oci://registry-1.docker.io/bitnamicharts/keycloak

Introduction

Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads.

This chart bootstraps a Keycloak deployment on a Kubernetes cluster using the Helm package manager.

Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Looking to use Keycloak in production? Try VMware Application Catalog, the enterprise edition of Bitnami Application Catalog.

Prerequisites

  • Kubernetes 1.19+
  • Helm 3.2.0+

Installing the Chart

To install the chart with the release name my-release:

helm install my-release oci://registry-1.docker.io/bitnamicharts/keycloak

These commands deploy a Keycloak application on the Kubernetes cluster in the default configuration.

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Parameters

Global parameters

NameDescriptionValue
global.imageRegistryGlobal Docker image registry""
global.imagePullSecretsGlobal Docker registry secret names as an array[]
global.storageClassGlobal StorageClass for Persistent Volume(s)""

Common parameters

NameDescriptionValue
kubeVersionForce target Kubernetes version (using Helm capabilities if not set)""
nameOverrideString to partially override common.names.fullname""
fullnameOverrideString to fully override common.names.fullname""
namespaceOverrideString to fully override common.names.namespace""
commonLabelsLabels to add to all deployed objects{}
enableServiceLinksIf set to false, disable Kubernetes service links in the pod spectrue
commonAnnotationsAnnotations to add to all deployed objects{}
dnsPolicyDNS Policy for pod""
dnsConfigDNS Configuration pod{}
clusterDomainDefault Kubernetes cluster domaincluster.local
extraDeployArray of extra objects to deploy with the release[]
diagnosticMode.enabledEnable diagnostic mode (all probes will be disabled and the command will be overridden)false
diagnosticMode.commandCommand to override all containers in the the statefulset["sleep"]
diagnosticMode.argsArgs to override all containers in the the statefulset["infinity"]

Keycloak parameters

NameDescriptionValue
image.registryKeycloak image registrydocker.io
image.repositoryKeycloak image repositorybitnami/keycloak
image.tagKeycloak image tag (immutable tags are recommended)22.0.1-debian-11-r4
image.digestKeycloak image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag""
image.pullPolicyKeycloak image pull policyIfNotPresent
image.pullSecretsSpecify docker-registry secret names as an array[]
image.debugSpecify if debug logs should be enabledfalse
auth.adminUserKeycloak administrator useruser
auth.adminPasswordKeycloak administrator password for the new user""
auth.existingSecretExisting secret containing Keycloak admin password""
auth.passwordSecretKeyKey where the Keycloak admin password is being stored inside the existing secret.""
tls.enabledEnable TLS encryption. Required for HTTPs traffic.false
tls.autoGeneratedGenerate automatically self-signed TLS certificates. Currently only supports PEM certificatesfalse
tls.existingSecretExisting secret containing the TLS certificates per Keycloak replica""
tls.usePemUse PEM certificates as input instead of PKS12/JKS storesfalse
tls.truststoreFilenameTruststore filename inside the existing secretkeycloak.truststore.jks
tls.keystoreFilenameKeystore filename inside the existing secretkeycloak.keystore.jks
tls.keystorePasswordPassword to access the keystore when it's password-protected""
tls.truststorePasswordPassword to access the truststore when it's password-protected""
tls.passwordsSecretSecret containing the Keystore and Truststore passwords.""
spi.existingSecretExisting secret containing the Keycloak truststore for SPI connection over HTTPS/TLS""
spi.truststorePasswordPassword to access the truststore when it's password-protected""
spi.truststoreFilenameTruststore filename inside the existing secretkeycloak-spi.truststore.jks
spi.passwordsSecretSecret containing the SPI Truststore passwords.""
spi.hostnameVerificationPolicyVerify the hostname of the server’s certificate. Allowed values: "ANY", "WILDCARD", "STRICT".""
productionRun Keycloak in production mode. TLS configuration is required except when using proxy=edge.false
proxyreverse Proxy mode edge, reencrypt, passthrough or nonepassthrough
httpRelativePathSet the path relative to '/' for serving resources. Useful if you are migrating from older version which were using '/auth/'/
configurationKeycloak Configuration. Auto-generated based on other parameters when not specified""
existingConfigmapName of existing ConfigMap with Keycloak configuration""
extraStartupArgsExtra default startup args""
initdbScriptsDictionary of initdb scripts{}
initdbScriptsConfigMapConfigMap with the initdb scripts (Note: Overrides initdbScripts)""
commandOverride default container command (useful when using custom images)[]
argsOverride default container args (useful when using custom images)[]
extraEnvVarsExtra environment variables to be set on Keycloak container[]
extraEnvVarsCMName of existing ConfigMap containing extra env vars""
extraEnvVarsSecretName of existing Secret containing extra env vars""

Keycloak statefulset parameters

NameDescriptionValue
replicaCountNumber of Keycloak replicas to deploy1
containerPorts.httpKeycloak HTTP container port8080
containerPorts.httpsKeycloak HTTPS container port8443
containerPorts.infinispanKeycloak infinispan container port7800
extraContainerPortsOptionally specify extra list of additional port-mappings for Keycloak container[]
podSecurityContext.enabledEnabled Keycloak pods' Security Contexttrue
podSecurityContext.fsGroupSet Keycloak pod's Security Context fsGroup1001
containerSecurityContext.enabledEnabled Keycloak containers' Security Contexttrue
containerSecurityContext.runAsUserSet Keycloak container's Security Context runAsUser1001
containerSecurityContext.runAsNonRootSet Keycloak container's Security Context runAsNonRoottrue
resources.limitsThe resources limits for the Keycloak containers{}
resources.requestsThe requested resources for the Keycloak containers{}
livenessProbe.enabledEnable livenessProbe on Keycloak containerstrue
livenessProbe.initialDelaySecondsInitial delay seconds for livenessProbe300
livenessProbe.periodSecondsPeriod seconds for livenessProbe1
livenessProbe.timeoutSecondsTimeout seconds for livenessProbe5
livenessProbe.failureThresholdFailure threshold for livenessProbe3
livenessProbe.successThresholdSuccess threshold for livenessProbe1
readinessProbe.enabledEnable readinessProbe on Keycloak containerstrue
readinessProbe.initialDelaySecondsInitial delay seconds for readinessProbe30
readinessProbe.periodSecondsPeriod seconds for readinessProbe10
readinessProbe.timeoutSecondsTimeout seconds for readinessProbe1
readinessProbe.failureThresholdFailure threshold for readinessProbe3
readinessProbe.successThresholdSuccess threshold for readinessProbe1
startupProbe.enabledEnable startupProbe on Keycloak containersfalse
startupProbe.initialDelaySecondsInitial delay seconds for startupProbe30
startupProbe.periodSecondsPeriod seconds for startupProbe5
startupProbe.timeoutSecondsTimeout seconds for startupProbe1
startupProbe.failureThresholdFailure threshold for startupProbe60
startupProbe.successThresholdSuccess threshold for startupProbe1
customLivenessProbeCustom Liveness probes for Keycloak{}
customReadinessProbeCustom Rediness probes Keycloak{}
customStartupProbeCustom Startup probes for Keycloak{}
lifecycleHooksLifecycleHooks to set additional configuration at startup{}
hostAliasesDeployment pod host aliases[]
podLabelsExtra labels for Keycloak pods{}
podAnnotationsAnnotations for Keycloak pods{}
podAffinityPresetPod affinity preset. Ignored if affinity is set. Allowed values: soft or hard""
podAntiAffinityPresetPod anti-affinity preset. Ignored if affinity is set. Allowed values: soft or hardsoft
nodeAffinityPreset.typeNode affinity preset type. Ignored if affinity is set. Allowed values: soft or hard""
nodeAffinityPreset.keyNode label key to match. Ignored if affinity is set.""
nodeAffinityPreset.valuesNode label values to match. Ignored if affinity is set.[]
affinityAffinity for pod assignment{}
nodeSelectorNode labels for pod assignment{}
tolerationsTolerations for pod assignment[]
topologySpreadConstraintsTopology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template[]
podManagementPolicyPod management policy for the Keycloak statefulsetParallel
priorityClassNameKeycloak pods' Priority Class Name""
schedulerNameUse an alternate scheduler, e.g. "stork".""
terminationGracePeriodSecondsSeconds Keycloak pod needs to terminate gracefully""
updateStrategy.typeKeycloak statefulset strategy typeRollingUpdate
updateStrategy.rollingUpdateKeycloak statefulset rolling update configuration parameters{}
extraVolumesOptionally specify extra list of additional volumes for Keycloak pods[]
extraVolumeMountsOptionally specify extra list of additional volumeMounts for Keycloak container(s)[]
initContainersAdd additional init containers to the Keycloak pods[]
sidecarsAdd additional sidecar containers to the Keycloak pods[]

Exposure parameters

NameDescriptionValue
service.typeKubernetes service typeClusterIP
service.http.enabledEnable http port on servicetrue
service.ports.httpKeycloak service HTTP port80
service.ports.httpsKeycloak service HTTPS port443
service.nodePortsSpecify the nodePort values for the LoadBalancer and NodePort service types.{}
service.sessionAffinityControl where client requests go, to the same pod or round-robinNone
service.sessionAffinityConfigAdditional settings for the sessionAffinity{}
service.clusterIPKeycloak service clusterIP IP""
service.loadBalancerIPloadBalancerIP for the SuiteCRM Service (optional, cloud specific)""
service.loadBalancerSourceRangesAddress that are allowed when service is LoadBalancer[]
service.externalTrafficPolicyEnable client source IP preservationCluster
service.annotationsAdditional custom annotations for Keycloak service{}
service.extraPortsExtra port to expose on Keycloak service[]
service.extraHeadlessPortsExtra ports to expose on Keycloak headless service[]
service.headless.annotationsAnnotations for the headless service.{}
service.headless.extraPortsExtra ports to expose on Keycloak headless service[]
ingress.enabledEnable ingress record generation for Keycloakfalse
ingress.ingressClassNameIngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)""
ingress.pathTypeIngress path typeImplementationSpecific
ingress.apiVersionForce Ingress API version (automatically detected if not set)""
ingress.hostnameDefault host for the ingress record (evaluated as template)keycloak.local
ingress.pathDefault path for the ingress record (evaluated as template)""
ingress.servicePortBackend service port to usehttp
ingress.annotationsAdditional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.{}
ingress.labelsAdditional labels for the Ingress resource.{}
ingress.tlsEnable TLS configuration for the host defined at ingress.hostname parameterfalse
ingress.selfSignedCreate a TLS secret for this ingress record using self-signed certificates generated by Helmfalse
ingress.extraHostsAn array with additional hostname(s) to be covered with the ingress record[]
ingress.extraPathsAny additional arbitrary paths that may need to be added to the ingress under the main host.[]
ingress.extraTlsThe tls configuration for additional hostnames to be covered with this ingress record.[]
ingress.secretsIf you're providing your own certificates, please use this to add the certificates as secrets[]
ingress.extraRulesAdditional rules to be covered with this ingress record[]
networkPolicy.enabledEnable the default NetworkPolicy policyfalse
networkPolicy.allowExternalDon't require client label for connectionstrue
networkPolicy.additionalRulesAdditional NetworkPolicy rules{}

RBAC parameter

NameDescriptionValue
serviceAccount.createEnable the creation of a ServiceAccount for Keycloak podstrue
serviceAccount.nameName of the created ServiceAccount""
serviceAccount.automountServiceAccountTokenAuto-mount the service account token in the podtrue
serviceAccount.annotationsAdditional custom annotations for the ServiceAccount{}
serviceAccount.extraLabelsAdditional labels for the ServiceAccount{}
rbac.createWhether to create and use RBAC resources or notfalse
rbac.rulesCustom RBAC rules[]

Other parameters

NameDescriptionValue
pdb.createEnable/disable a Pod Disruption Budget creationfalse
pdb.minAvailableMinimum number/percentage of pods that should remain scheduled1
pdb.maxUnavailableMaximum number/percentage of pods that may be made unavailable""
autoscaling.enabledEnable autoscaling for Keycloakfalse
autoscaling.minReplicasMinimum number of Keycloak replicas1
autoscaling.maxReplicasMaximum number of Keycloak replicas11
autoscaling.targetCPUTarget CPU utilization percentage""
autoscaling.targetMemoryTarget Memory utilization percentage""

Metrics parameters

NameDescriptionValue
metrics.enabledEnable exposing Keycloak statisticsfalse
metrics.service.ports.httpMetrics service HTTP port8080
metrics.service.annotationsAnnotations for enabling prometheus to access the metrics endpoints{}
metrics.serviceMonitor.enabledCreate ServiceMonitor Resource for scraping metrics using PrometheusOperatorfalse
metrics.serviceMonitor.portMetrics service HTTP porthttp
metrics.serviceMonitor.endpointsThe endpoint configuration of the ServiceMonitor. Path is mandatory. Interval, timeout and labellings can be overwritten.[]
metrics.serviceMonitor.pathMetrics service HTTP path. Deprecated: Use @param metrics.serviceMonitor.endpoints instead""
metrics.serviceMonitor.namespaceNamespace which Prometheus is running in""
metrics.serviceMonitor.intervalInterval at which metrics should be scraped30s
metrics.serviceMonitor.scrapeTimeoutSpecify the timeout after which the scrape is ended""
metrics.serviceMonitor.labelsAdditional labels that can be used so ServiceMonitor will be discovered by Prometheus{}
metrics.serviceMonitor.selectorPrometheus instance selector labels{}
metrics.serviceMonitor.relabelingsRelabelConfigs to apply to samples before scraping[]
metrics.serviceMonitor.metricRelabelingsMetricRelabelConfigs to apply to samples before ingestion[]
metrics.serviceMonitor.honorLabelshonorLabels chooses the metric's labels on collisions with target labelsfalse
metrics.serviceMonitor.jobLabelThe name of the label on the target service to use as the job name in prometheus.""
metrics.prometheusRule.enabledCreate PrometheusRule Resource for scraping metrics using PrometheusOperatorfalse
metrics.prometheusRule.namespaceNamespace which Prometheus is running in""
metrics.prometheusRule.labelsAdditional labels that can be used so PrometheusRule will be discovered by Prometheus{}
metrics.prometheusRule.groupsGroups, containing the alert rules.[]

keycloak-config-cli parameters

NameDescriptionValue
keycloakConfigCli.enabledWhether to enable keycloak-config-cli jobfalse
keycloakConfigCli.image.registrykeycloak-config-cli container image registrydocker.io
keycloakConfigCli.image.repositorykeycloak-config-cli container image repositorybitnami/keycloak-config-cli
keycloakConfigCli.image.tagkeycloak-config-cli container image tag5.8.0-debian-11-r5
keycloakConfigCli.image.digestkeycloak-config-cli container image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag""
keycloakConfigCli.image.pullPolicykeycloak-config-cli container image pull policyIfNotPresent
keycloakConfigCli.image.pullSecretskeycloak-config-cli container image pull secrets[]
keycloakConfigCli.annotationsAnnotations for keycloak-config-cli job{}
keycloakConfigCli.commandCommand for running the container (set to default if not set). Use array form[]
keycloakConfigCli.argsArgs for running the container (set to default if not set). Use array form[]
keycloakConfigCli.hostAliasesJob pod host aliases[]
keycloakConfigCli.resources.limitsThe resources limits for the keycloak-config-cli container{}
keycloakConfigCli.resources.requestsThe requested resources for the keycloak-config-cli container{}
keycloakConfigCli.containerSecurityContext.enabledEnabled keycloak-config-cli containers' Security Contexttrue
keycloakConfigCli.containerSecurityContext.runAsUserSet keycloak-config-cli container's Security Context runAsUser1001
keycloakConfigCli.containerSecurityContext.runAsNonRootSet keycloak-config-cli container's Security Context runAsNonRoottrue
keycloakConfigCli.podSecurityContext.enabledEnabled keycloak-config-cli pods' Security Contexttrue
keycloakConfigCli.podSecurityContext.fsGroupSet keycloak-config-cli pod's Security Context fsGroup1001
keycloakConfigCli.backoffLimitNumber of retries before considering a Job as failed1
keycloakConfigCli.podLabelsPod extra labels{}
keycloakConfigCli.podAnnotationsAnnotations for job pod{}
keycloakConfigCli.extraEnvVarsAdditional environment variables to set[]
keycloakConfigCli.nodeSelectorNode labels for pod assignment{}
keycloakConfigCli.podTolerationsTolerations for job pod assignment[]
keycloakConfigCli.extraEnvVarsCMConfigMap with extra environment variables""
keycloakConfigCli.extraEnvVarsSecretSecret with extra environment variables""
keycloakConfigCli.extraVolumesExtra volumes to add to the job[]
keycloakConfigCli.extraVolumeMountsExtra volume mounts to add to the container[]
keycloakConfigCli.initContainersAdd additional init containers to the Keycloak config cli pod[]
keycloakConfigCli.sidecarsAdd additional sidecar containers to the Keycloak config cli pod[]
keycloakConfigCli.configurationkeycloak-config-cli realms configuration{}
keycloakConfigCli.existingConfigmapConfigMap with keycloak-config-cli configuration. This will override keycloakConfigCli.config""
keycloakConfigCli.cleanupAfterFinished.enabledEnables Cleanup for Finished Jobsfalse
keycloakConfigCli.cleanupAfterFinished.secondsSets the value of ttlSecondsAfterFinished600

Database parameters

NameDescriptionValue
postgresql.enabledSwitch to enable or disable the PostgreSQL helm charttrue
postgresql.auth.postgresPasswordPassword for the "postgres" admin user. Ignored if auth.existingSecret with key postgres-password is provided""
postgresql.auth.usernameName for a custom user to createbn_keycloak
postgresql.auth.passwordPassword for the custom user to create""
postgresql.auth.databaseName for a custom database to createbitnami_keycloak
postgresql.auth.existingSecretName of existing secret to use for PostgreSQL credentials""
postgresql.architecturePostgreSQL architecture (standalone or replication)standalone
externalDatabase.hostDatabase host""
externalDatabase.portDatabase port number5432
externalDatabase.userNon-root username for Keycloakbn_keycloak
externalDatabase.passwordPassword for the non-root username for Keycloak""
externalDatabase.databaseKeycloak database namebitnami_keycloak
externalDatabase.existingSecretName of an existing secret resource containing the database credentials""
externalDatabase.existingSecretHostKeyName of an existing secret key containing the database host name""
externalDatabase.existingSecretPortKeyName of an existing secret key containing the database port""
externalDatabase.existingSecretUserKeyName of an existing secret key containing the database user""
externalDatabase.existingSecretDatabaseKeyName of an existing secret key containing the database name""
externalDatabase.existingSecretPasswordKeyName of an existing secret key containing the database credentials""

Keycloak Cache parameters

NameDescriptionValue
cache.enabledSwitch to enable or disable the keycloak distributed cache for kubernetes.true
cache.stackNameSet infinispan cache stack to usekubernetes
cache.stackFileSet infinispan cache stack filename to use""

Keycloak Logging parameters

NameDescriptionValue
logging.outputAlternates between the default log output format or json formatdefault
logging.levelAllowed values as documented: FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL, OFFINFO

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install my-release --set auth.adminPassword=secretpassword oci://registry-1.docker.io/bitnamicharts/keycloak

The above command sets the Keycloak administrator password to secretpassword.

NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

helm install my-release -f values.yaml oci://registry-1.docker.io/bitnamicharts/keycloak

Tip: You can use the default values.yaml

Keycloak realms, users and clients can be created from the Keycloak administration panel. Refer to the tutorial on adding user authentication to applications with Keycloak for more details on these operations.

Configuration and installation details

Rolling vs Immutable tags

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.

Use an external database

Sometimes, you may want to have Keycloak connect to an external PostgreSQL database rather than a database within your cluster - for example, when using a managed database service, or when running a single database server for all your applications. To do this, set the postgresql.enabled parameter to false and specify the credentials for the external database using the externalDatabase.* parameters.

Refer to the chart documentation on using an external database for more details and an example.

NOTE: Only PostgreSQL database server is supported as external database

It is not supported but possible to run Keycloak with an external MSSQL database with the following settings:

externalDatabase:
  host: "mssql.example.com"
  port: 1433
  user: keycloak
  database: keycloak
  existingSecret: passwords
extraEnvVars:
  - name: KC_DB # override values from the conf file
    value: 'mssql'
  - name: KC_DB_URL
    value: 'jdbc:sqlserver://mssql.example.com:1433;databaseName=keycloak;'

Add extra environment variables

In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the extraEnvVars property.

extraEnvVars:
  - name: KEYCLOAK_LOG_LEVEL
    value: DEBUG

Alternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the extraEnvVarsCM or the extraEnvVarsSecret values.

Use Sidecars and Init Containers

If additional containers are needed in the same pod (such as additional metrics or logging exporters), they can be defined using the sidecars config parameter. Similarly, extra init containers can be added using the initContainers parameter.

Refer to the chart documentation for more information on, and examples of, configuring and using sidecars and init containers.

Initialize a fresh instance

The Bitnami Keycloak image allows you to use your custom scripts to initialize a fresh instance. In order to execute the scripts, you can specify custom scripts using the initdbScripts parameter as dict.

In addition to this option, you can also set an external ConfigMap with all the initialization scripts. This is done by setting the initdbScriptsConfigMap parameter. Note that this will override the previous option.

The allowed extensions is .sh.

Deploy extra resources

There are cases where you may want to deploy extra objects, such a ConfigMap containing your app's configuration or some extra deployment with a micro service used by your app. For covering this case, the chart allows adding the full specification of other objects using the extraDeploy parameter.

Set Pod affinity

This chart allows you to set your custom affinity using the affinity parameter. Find more information about Pod's affinity in the kubernetes documentation.

As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters.

Configure Ingress

This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as nginx-ingress-controller or contour you can utilize the ingress controller to serve your application.

To enable Ingress integration, set ingress.enabled to true. The ingress.hostname property can be used to set the host name. The ingress.tls parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. Learn more about configuring and using Ingress.

Configure TLS Secrets for use with Ingress

The chart also facilitates the creation of TLS secrets for use with the Ingress controller, with different options for certificate management. Learn more about TLS secrets.

Use with ingress offloading SSL

If your ingress controller has the SSL Termination, you should set proxy to edge.

Manage secrets and passwords

This chart provides several ways to manage passwords:

  • Values passed to the chart
  • An existing secret with all the passwords (via the existingSecret parameter)
  • Multiple existing secrets with all the passwords (via the existingSecretPerPassword parameter)

Refer to the chart documentation on managing passwords for examples of each method.

Troubleshooting

Find more information about how to deal with common errors related to Bitnami's Helm charts in this troubleshooting guide.

Upgrading

To 15.0.0

This major updates the default serviceType from LoadBalancer to ClusterIP to avoid inadvertently exposing Keycloak directly to the internet without an Ingress.

To 12.0.0

This major updates the PostgreSQL subchart to its newest major, 12.0.0. Here you can find more information about the changes introduced in that version.

To any previous version

Refer to the chart documentation for more information about how to upgrade from previous releases.

License

Copyright © 2023 VMware, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.