charts/bitnami/kong

Kong packaged by Bitnami

Kong is an open source Microservice API gateway and platform designed for managing microservices requests of high-availability, fault-tolerance, and distributed systems.

Overview of Kong

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 repo add bitnami https://charts.bitnami.com/bitnami
  helm install my-release bitnami/kong

Introduction

This chart bootstraps a kong deployment on a Kubernetes cluster using the Helm package manager. It also includes the kong-ingress-controller container for managing Ingress resources using Kong.

Extra functionalities beyond the Kong core are extended through plugins. Kong is built on top of reliable technologies like NGINX and provides an easy-to-use RESTful API to operate and configure the system.

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

Prerequisites

• Kubernetes 1.19+
• Helm 3.2.0+
• PV provisioner support in the underlying infrastructure

Installing the Chart

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

  helm repo add bitnami https://charts.bitnami.com/bitnami
  helm install my-release bitnami/kong

These commands deploy kong on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip

: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

  helm delete my-release

Parameters

Global parameters

Name	Description	Value
global.imageRegistry	Global Docker image registry	""
global.imagePullSecrets	Global Docker registry secret names as an array	[]
global.storageClass	Global StorageClass for Persistent Volume(s)	""

Common parameters

Name	Description	Value
kubeVersion	Force target Kubernetes version (using Helm capabilities if not set)	""
nameOverride	String to partially override kong.fullname template with a string (will prepend the release name)	""
fullnameOverride	String to fully override kong.fullname template with a string	""
commonAnnotations	Common annotations to add to all Kong resources (sub-charts are not considered). Evaluated as a template	{}
commonLabels	Common labels to add to all Kong resources (sub-charts are not considered). Evaluated as a template	{}
clusterDomain	Kubernetes cluster domain	cluster.local
extraDeploy	Array of extra objects to deploy with the release (evaluated as a template).	[]
diagnosticMode.enabled	Enable diagnostic mode (all probes will be disabled and the command will be overridden)	false
diagnosticMode.command	Command to override all containers in the deployment	["sleep"]
diagnosticMode.args	Args to override all containers in the deployment	["infinity"]

Deployment parameters

Name	Description	Value
image.registry	kong image registry	docker.io
image.repository	kong image repository	bitnami/kong
image.tag	kong image tag (immutable tags are recommended)	2.7.0-debian-10-r12
image.pullPolicy	kong image pull policy	IfNotPresent
image.pullSecrets	Specify docker-registry secret names as an array	[]
image.debug	Enable image debug mode	false
database	Select which database backend Kong will use. Can be 'postgresql' or 'cassandra'	postgresql
replicaCount	Number of replicas of the kong Pod	2
hostAliases	Add deployment host aliases	[]
updateStrategy.type	Set up update strategy for kong installation. Set to Recreate if you use persistent volume that cannot be mounted by more than one pods to makesure the pods is destroyed first.	RollingUpdate
schedulerName	Alternative scheduler	""
useDaemonset	Use a daemonset instead of a deployment. replicaCount will not take effect.	false
extraVolumes	Array of extra volumes to be added to the Kong deployment deployment (evaluated as template). Requires setting extraVolumeMounts	[]
initContainers	Add additional init containers to the pod (evaluated as a template)	[]
sidecars	Attach additional containers to the pod (evaluated as a template)	[]
containerSecurityContext.runAsUser	Set Kong container's Security Context runAsUser	1001
containerSecurityContext.runAsNonRoot	Set Kong container's Security Context runAsNonRoot	true
podSecurityContext	Pod security context	{}
nodeSelector	Node labels for pod assignment	{}
tolerations	Tolerations for pod assignment	[]
podAffinityPreset	Pod affinity preset. Ignored if affinity is set. Allowed values: soft or hard	""
podAntiAffinityPreset	Pod anti-affinity preset. Ignored if affinity is set. Allowed values: soft or hard	soft
nodeAffinityPreset.type	Node affinity preset type. Ignored if affinity is set. Allowed values: soft or hard	""
nodeAffinityPreset.key	Node label key to match Ignored if affinity is set.	""
nodeAffinityPreset.values	Node label values to match. Ignored if affinity is set.	[]
affinity	Affinity for pod assignment	{}
podAnnotations	Pod annotations	{}
podLabels	Pod labels	{}
autoscaling.enabled	Deploy a HorizontalPodAutoscaler object for the Kong deployment	false
autoscaling.apiVersion	API Version of the HPA object (for compatibility with Openshift)	autoscaling/v2beta1
autoscaling.minReplicas	Minimum number of replicas to scale back	2
autoscaling.maxReplicas	Maximum number of replicas to scale out	5
autoscaling.metrics	Metrics to use when deciding to scale the deployment (evaluated as a template)	[]
pdb.enabled	Deploy a pdb object for the Kong pod	false
pdb.maxUnavailable	Maximum unavailable Kong replicas (expressed in percentage)	50%

Traffic Exposure Parameters

Name	Description	Value
service.type	Kubernetes Service type	ClusterIP
service.clusterIP	Cluster internal IP of the service	""
service.externalTrafficPolicy	external traffic policy managing client source IP preservation	""
service.proxyHttpPort	kong proxy HTTP service port port	80
service.proxyHttpsPort	kong proxy HTTPS service port port	443
service.exposeAdmin	Add the Kong Admin ports to the service	false
service.adminHttpPort	kong admin HTTPS service port (only if service.exposeAdmin=true)	8001
service.adminHttpsPort	kong admin HTTPS service port (only if service.exposeAdmin=true)	8444
service.disableHttpPort	Disable Kong proxy HTTP and Kong admin HTTP ports	false
service.proxyHttpNodePort	Port to bind to for NodePort service type (proxy HTTP)	""
service.proxyHttpsNodePort	Port to bind to for NodePort service type (proxy HTTPS)	""
service.adminHttpNodePort	Port to bind to for NodePort service type (admin HTTP)	""
service.adminHttpsNodePort	Port to bind to for NodePort service type (admin HTTPS)	""
service.loadBalancerIP	loadBalancerIP if kong service type is LoadBalancer	""
service.annotations	Annotations for kong service	{}
service.extraPorts	Extra ports to expose (normally used with the sidecar value)	[]
ingress.enabled	Enable ingress controller resource	false
ingress.pathType	Ingress path type	ImplementationSpecific
ingress.apiVersion	Force Ingress API version (automatically detected if not set)	""
ingress.hostname	Default host for the ingress resource	kong.local
ingress.path	Ingress path	/
ingress.annotations	Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.	{}
ingress.tls	Create TLS Secret	false
ingress.extraHosts	The list of additional hostnames to be covered with this ingress record.	[]
ingress.extraPaths	Additional arbitrary path/backend objects	[]
ingress.extraTls	The tls configuration for additional hostnames to be covered with this ingress record.	[]
ingress.secrets	If you're providing your own certificates, please use this to add the certificates as secrets	[]

Kong Container Parameters

Name	Description	Value
kong.command	Override default container command (useful when using custom images)	[]
kong.args	Override default container args (useful when using custom images)	[]
kong.initScriptsCM	Configmap with init scripts to execute	""
kong.initScriptsSecret	Configmap with init scripts to execute	""
kong.extraEnvVars	Array containing extra env vars to configure Kong	[]
kong.extraEnvVarsCM	ConfigMap containing extra env vars to configure Kong	""
kong.extraEnvVarsSecret	Secret containing extra env vars to configure Kong (in case of sensitive data)	""
kong.extraVolumeMounts	Array of extra volume mounts to be added to the Kong Container (evaluated as template). Normally used with extraVolumes.	[]
kong.customLivenessProbe	Override default liveness probe (kong container)	{}
kong.customReadinessProbe	Override default readiness probe (kong container)	{}
kong.livenessProbe.enabled	Enable livenessProbe	true
kong.livenessProbe.initialDelaySeconds	Initial delay seconds for livenessProbe	120
kong.livenessProbe.periodSeconds	Period seconds for livenessProbe	10
kong.livenessProbe.timeoutSeconds	Timeout seconds for livenessProbe	5
kong.livenessProbe.failureThreshold	Failure threshold for livenessProbe	6
kong.livenessProbe.successThreshold	Success threshold for livenessProbe	1
kong.readinessProbe.enabled	Enable readinessProbe	true
kong.readinessProbe.initialDelaySeconds	Initial delay seconds for readinessProbe	30
kong.readinessProbe.periodSeconds	Period seconds for readinessProbe	10
kong.readinessProbe.timeoutSeconds	Timeout seconds for readinessProbe	5
kong.readinessProbe.failureThreshold	Failure threshold for readinessProbe	6
kong.readinessProbe.successThreshold	Success threshold for readinessProbe	1
kong.lifecycleHooks	Lifecycle hooks (kong container)	{}
kong.resources.limits	The resources limits for the container	{}
kong.resources.requests	The requested resources for the container	{}

Kong Migration job Parameters

Name	Description	Value
migration.command	Override default container command (useful when using custom images)	[]
migration.args	Override default container args (useful when using custom images)	[]
migration.hostAliases	Add deployment host aliases	[]
migration.annotations	Add annotations to the job	{}
migration.extraEnvVars	Array containing extra env vars to configure the Kong migration job	[]
migration.extraEnvVarsCM	ConfigMap containing extra env vars to configure the Kong migration job	""
migration.extraEnvVarsSecret	Secret containing extra env vars to configure the Kong migration job (in case of sensitive data)	""
migration.extraVolumeMounts	Array of extra volume mounts to be added to the Kong Container (evaluated as template). Normally used with extraVolumes.	[]
migration.resources.limits	The resources limits for the container	{}
migration.resources.requests	The requested resources for the container	{}

Kong Ingress Controller Container Parameters

Name	Description	Value
ingressController.enabled	Enable/disable the Kong Ingress Controller	true
ingressController.customResourceDeletePolicy	Add custom CRD resource delete policy (for Helm 2 support)	{}
ingressController.image.registry	Kong Ingress Controller image registry	docker.io
ingressController.image.repository	Kong Ingress Controller image name	bitnami/kong-ingress-controller
ingressController.image.tag	Kong Ingress Controller image tag	2.1.1-debian-10-r0
ingressController.image.pullPolicy	kong ingress controller image pull policy	IfNotPresent
ingressController.image.pullSecrets	Specify docker-registry secret names as an array	[]
ingressController.proxyReadyTimeout	Maximum time (in seconds) to wait for the Kong container to be ready	300
ingressController.rbac.create	Create the necessary Service Accounts, Roles and Rolebindings for the Ingress Controller to work	true
ingressController.rbac.existingServiceAccount	Use an existing service account for all the RBAC operations	""
ingressController.ingressClass	Name of the class to register Kong Ingress Controller (useful when having other Ingress Controllers in the cluster)	kong
ingressController.command	Override default container command (useful when using custom images)	[]
ingressController.args	Override default container args (useful when using custom images)	[]
ingressController.extraEnvVars	Array containing extra env vars to configure Kong	[]
ingressController.extraEnvVarsCM	ConfigMap containing extra env vars to configure Kong Ingress Controller	""
ingressController.extraEnvVarsSecret	Secret containing extra env vars to configure Kong Ingress Controller (in case of sensitive data)	""
ingressController.extraVolumeMounts	Array of extra volume mounts to be added to the Kong Ingress Controller container (evaluated as template). Normally used with extraVolumes.	[]
ingressController.customLivenessProbe	Override default liveness probe (kong ingress controller container)	{}
ingressController.customReadinessProbe	Override default readiness probe (kong ingress controller container)	{}
ingressController.livenessProbe.enabled	Enable livenessProbe	true
ingressController.livenessProbe.initialDelaySeconds	Initial delay seconds for livenessProbe	120
ingressController.livenessProbe.periodSeconds	Period seconds for livenessProbe	10
ingressController.livenessProbe.timeoutSeconds	Timeout seconds for livenessProbe	5
ingressController.livenessProbe.failureThreshold	Failure threshold for livenessProbe	6
ingressController.livenessProbe.successThreshold	Success threshold for livenessProbe	1
ingressController.readinessProbe.enabled	Enable readinessProbe	true
ingressController.readinessProbe.initialDelaySeconds	Initial delay seconds for readinessProbe	30
ingressController.readinessProbe.periodSeconds	Period seconds for readinessProbe	10
ingressController.readinessProbe.timeoutSeconds	Timeout seconds for readinessProbe	5
ingressController.readinessProbe.failureThreshold	Failure threshold for readinessProbe	6
ingressController.readinessProbe.successThreshold	Success threshold for readinessProbe	1
ingressController.resources.limits	The resources limits for the container	{}
ingressController.resources.requests	The requested resources for the container	{}

PostgreSQL Parameters

Name	Description	Value
postgresql.enabled	Deploy the PostgreSQL sub-chart	true
postgresql.usePasswordFile	Mount the PostgreSQL secret as a file	false
postgresql.external.host	Host of an external PostgreSQL installation	""
postgresql.external.user	Username of the external PostgreSQL installation	""
postgresql.external.password	Password of the external PostgreSQL installation	""
postgresql.existingSecret	Use an existing secret file with the PostgreSQL password (can be used with the bundled chart or with an existing installation)	""
postgresql.postgresqlDatabase	Database name to be used by Kong	kong
postgresql.postgresqlUsername	Username to be created by the PostgreSQL bundled chart	kong

Cassandra Parameters

Name	Description	Value
cassandra.enabled	Deploy the Cassandra sub-chart	false
cassandra.dbUser.user	Username to be created by the cassandra bundled chart	kong
cassandra.usePasswordFile	Mount the Cassandra secret as a file	false
cassandra.external.hosts	Hosts of an external cassandra installation	[]
cassandra.external.port	Port of an external cassandra installation	9042
cassandra.external.user	Username of the external cassandra installation	""
cassandra.external.password	Password of the external cassandra installation	""
cassandra.existingSecret	Use an existing secret file with the Cassandra password (can be used with the bundled chart or with an existing installation)	""

Metrics Parameters

Name	Description	Value
metrics.enabled	Enable the export of Prometheus metrics	false
metrics.service.annotations	Annotations for Prometheus metrics service	{}
metrics.service.type	Type of the Prometheus metrics service	ClusterIP
metrics.service.port	Port of the Prometheus metrics service	9119
metrics.serviceMonitor.enabled	If true, creates a Prometheus Operator ServiceMonitor (also requires metrics.enabled to be true)	false
metrics.serviceMonitor.namespace	Namespace in which Prometheus is running	""
metrics.serviceMonitor.serviceAccount	Service account used by Prometheus	""
metrics.serviceMonitor.interval	Interval at which metrics should be scraped.	""
metrics.serviceMonitor.scrapeTimeout	Timeout after which the scrape is ended	""
metrics.serviceMonitor.selector	Prometheus instance selector labels	{}
metrics.serviceMonitor.rbac.enabled	Whether to enable RBAC	true

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

  helm install my-release \
  --set service.exposeAdmin=true bitnami/kong

The above command exposes the Kong admin ports inside the Kong service.

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 bitnami/kong

Tip

: You can use the default values.yaml

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.

Database backend

The Bitnami Kong chart allows setting two database backends: PostgreSQL or Cassandra. For each option, there are two extra possibilities: deploy a sub-chart with the database installation or use an existing one. The list below details the different options (replace the placeholders specified between UNDERSCORES):

• Deploy the PostgreSQL sub-chart (default)

  helm install my-release bitnami/kong

• Use an external PostgreSQL database

  helm install my-release bitnami/kong \
    --set postgresql.enabled=false \
    --set postgresql.external.host=_HOST_OF_YOUR_POSTGRESQL_INSTALLATION_ \
    --set postgresql.external.password=_PASSWORD_OF_YOUR_POSTGRESQL_INSTALLATION_ \
    --set postgresql.external.user=_USER_OF_YOUR_POSTGRESQL_INSTALLATION_

• Deploy the Cassandra sub-chart

  helm install my-release bitnami/kong \
    --set database=cassandra \
    --set postgresql.enabled=false \
    --set cassandra.enabled=true

• Use an existing Cassandra installation

  helm install my-release bitnami/kong \
    --set database=cassandra \
    --set postgresql.enabled=false \
    --set cassandra.enabled=false \
    --set cassandra.external.hosts[0]=_CONTACT_POINT_0_OF_YOUR_CASSANDRA_CLUSTER_ \
    --set cassandra.external.hosts[1]=_CONTACT_POINT_1_OF_YOUR_CASSANDRA_CLUSTER_ \
    ...
    --set cassandra.external.user=_USER_OF_YOUR_CASSANDRA_INSTALLATION_ \
    --set cassandra.external.password=_PASSWORD_OF_YOUR_CASSANDRA_INSTALLATION_

DB-less

Kong 1.1 added the capability to run Kong without a database, using only in-memory storage for entities: we call this DB-less mode. When running Kong DB-less, the configuration of entities is done in a second configuration file, in YAML or JSON, using declarative configuration (ref. Link). As is said in step 4 of kong official docker installation, just add the env variable "KONG_DATABASE=off".

How to enable it

1. Set database value with any value other than "postgresql" or "cassandra". For example database: "off"
2. Use kong.extraEnvVars value to set the KONG_DATABASE environment variable:

kong.extraEnvVars:
- name: KONG_DATABASE
  value: "off"

Sidecars and Init Containers

If you have a need for additional containers to run within the same pod as Kong (e.g. an additional metrics or logging exporter), you can do so via the sidecars config parameter. Simply define your container according to the Kubernetes container spec.

sidecars:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
       containerPort: 1234

Similarly, you can add extra init containers using the initContainers parameter.

initContainers:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
        containerPort: 1234

Adding extra environment variables

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

kong:
  extraEnvVars:
    - name: KONG_LOG_LEVEL
      value: error

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

The Kong Ingress Controller and the Kong Migration job also allow this kind of configuration via the ingressController.extraEnvVars, ingressController.extraEnvVarsCM, ingressController.extraEnvVarsSecret, migration.extraEnvVars, migration.extraEnvVarsCM and migration.extraEnvVarsSecret values.

Using custom init scripts

For advanced operations, the Bitnami Kong charts allows using custom init scripts that will be mounted in /docker-entrypoint.init-db. You can use a ConfigMap or a Secret (in case of sensitive data) for mounting these extra scripts. Then use the kong.initScriptsCM and kong.initScriptsSecret values.

elasticsearch.hosts[0]=elasticsearch-host
elasticsearch.port=9200
initScriptsCM=special-scripts
initScriptsSecret=special-scripts-sensitive

Deploying extra resources

There are cases where you may want to deploy extra objects, such as KongPlugins, KongConsumers, amongst others. For covering this case, the chart allows adding the full specification of other objects using the extraDeploy parameter. The following example would activate a plugin at deployment time.

## Extra objects to deploy (value evaluated as a template)
##
extraDeploy: |-
  - apiVersion: configuration.konghq.com/v1
    kind: KongPlugin
    metadata:
      name: {{ include "common.names.fullname" . }}-plugin-correlation
      namespace: {{ .Release.Namespace }}
      labels: {{- include "common.labels.standard" . | nindent 6 }}
    config:
      header_name: my-request-id
    plugin: correlation-id

Setting Pod's 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.

Troubleshooting

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

Upgrading

It's necessary to specify the existing passwords while performing a upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the postgresql.postgresqlPassword or cassandra.password parameters when upgrading the chart:

$ helm upgrade my-release bitnami/kong \
    --set database=postgresql
    --set postgresql.enabled=true
    --set
    --set postgresql.postgresqlPassword=[POSTGRESQL_PASSWORD]

Note: you need to substitute the placeholders [POSTGRESQL_PASSWORD] with the values obtained from instructions in the installation notes.

To 5.0.0

The cassandra sub-chart was upgraded to 9.x.x. Several values of the sub-chart were changed, so please check the upgrade notes.

No issues are expected during the upgrade.

To 3.1.0

Kong Ingress Controller version was bumped to new major version, 1.x.x. The associated CRDs were updated accordingly.

To 3.0.0

On November 13, 2020, Helm v2 support was formally finished, this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.

What changes were introduced in this major version?

• Previous versions of this Helm Chart use apiVersion: v1 (installable by both Helm 2 and 3), this Helm Chart was updated to apiVersion: v2 (installable by Helm 3 only). Here you can find more information about the apiVersion field.
• Move dependency information from the requirements.yaml to the Chart.yaml
• After running helm dependency update, a Chart.lock file is generated containing the same structure used in the previous requirements.lock
• The different fields present in the Chart.yaml file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
• This chart depends on the PostgreSQL 10 instead of PostgreSQL 9. Apart from the same changes that are described in this section, there are also other major changes due to the master/slave nomenclature was replaced by primary/readReplica. Here you can find more information about the changes introduced.

Considerations when upgrading to this version

• If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
• If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the official Helm documentation about migrating from Helm v2 to v3
• If you want to upgrade to this version from a previous one installed with Helm v3, it should be done reusing the PVC used to hold the PostgreSQL data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is kong):

NOTE: Please, create a backup of your database before running any of those actions.

Export secrets and required values to update

$ export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default kong-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
$ export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=kong,app.kubernetes.io/name=postgresql,role=master -o jsonpath="{.items[0].metadata.name}")

Delete statefulsets

Delete PostgreSQL statefulset. Notice the option --cascade=false:

$ kubectl delete statefulsets.apps kong-postgresql --cascade=false

Upgrade the chart release

$ helm upgrade kong bitnami/kong \
    --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD \
    --set postgresql.persistence.existingClaim=$POSTGRESQL_PVC

Force new statefulset to create a new pod for postgresql

$ kubectl delete pod kong-postgresql-0

Finally, you should see the lines below in MariaDB container logs:

$ kubectl logs $(kubectl get pods -l app.kubernetes.io/instance=postgresql,app.kubernetes.io/name=postgresql,role=primary -o jsonpath="{.items[0].metadata.name}")
...
postgresql 08:05:12.59 INFO  ==> Deploying PostgreSQL with persisted data...
...

Useful links

• https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
• https://helm.sh/docs/topics/v2_v3_migration/
• https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/

To 4.0.0

This major updates the Cassandra subchart to its newest major, 4.0.0. Here you can find more information about the changes introduced in those versions.

To 2.0.0

PostgreSQL and Cassandra dependencies versions were bumped to new major versions, 9.x.x and 6.x.x respectively. Both of these include breaking changes and hence backwards compatibility is no longer guaranteed.

In order to properly migrate your data to this new version:

• If you were using PostgreSQL as your database, please refer to the PostgreSQL Upgrade Notes.

• If you were using Cassandra as your database, please refer to the Cassandra Upgrade Notes.

License

Copyright © 2022 Bitnami

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.