From 2985e973e67c51af4abd4ab5a643dc5d43fc02db Mon Sep 17 00:00:00 2001 From: Harry Date: Thu, 7 Nov 2019 13:57:42 -0600 Subject: [PATCH] [stable/kong] major breaking change: dbless and KIC by-default (#18613) Also, a changelog section has been started that should be updated for each and every release. Signed-off-by: Harry Bagdi --- stable/kong/Chart.yaml | 2 +- stable/kong/README.md | 24 ++++++++++++++++++------ stable/kong/values.yaml | 14 +++++++------- 3 files changed, 26 insertions(+), 14 deletions(-) diff --git a/stable/kong/Chart.yaml b/stable/kong/Chart.yaml index 884f995856..0aa873c702 100644 --- a/stable/kong/Chart.yaml +++ b/stable/kong/Chart.yaml @@ -12,5 +12,5 @@ maintainers: name: kong sources: - https://github.com/Kong/kong -version: 0.26.1 +version: 0.27.0 appVersion: 1.3 diff --git a/stable/kong/README.md b/stable/kong/README.md index c19ee40dc0..ddf2b9f1e3 100644 --- a/stable/kong/README.md +++ b/stable/kong/README.md @@ -137,9 +137,11 @@ for the service definition to work properly. ### Kong-specific parameters -Kong has a choice of either Postgres or Cassandra as a backend datatstore. -This chart allows you to choose either of them with the `env.database` -parameter. Postgres is chosen by default. +Kong can run and store all it's configuration in-memory or it can be backed +using a database. Kong supports Postgres and Cassandra. +This chart by default installs Kong without a database, storing all the +configuration in-memory. If you'd like to use a database, you can deploy one +and set the 'env.database` property accordingly. This chart allows you to bring your own database that you manage or spin up separately (recommended) or spin up a new Postgres instance using @@ -152,11 +154,11 @@ that via the `env.database` parameter. | Parameter | Description | Default | | ------------------------------| ------------------------------------------------------------------------| ----------------------| -| postgresql.enabled | Spin up a new postgres instance for Kong | `true` | +| postgresql.enabled | Spin up a new postgres instance for Kong | `false` | | waitImage.repository | Image used to wait for database to become ready | `busybox` | | waitImage.tag | Tag for image used to wait for database to become ready | `latest` | | waitImage.pullPolicy | Wait image pull policy | `IfNotPresent` | -| env.database | Choose either `postgres`, `cassandra` or `"off"` (for dbless mode) | `postgres` | +| env.database | Choose either `postgres`, `cassandra` or `"off"` (for dbless mode) | `off` | | env.pg_user | Postgres username | `kong` | | env.pg_database | Postgres database name | `kong` | | env.pg_password | Postgres database password (required if you are using your own database)| `kong` | @@ -388,7 +390,7 @@ You can can learn about kong ingress custom resource definitions [here](https:// | Parameter | Description | Default | | ---------------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | -| enabled | Deploy the ingress controller, rbac and crd | false | +| enabled | Deploy the ingress controller, rbac and crd | true | | replicaCount | Number of desired ingress controllers | 1 | | image.repository | Docker image with the ingress controller | kong-docker-kubernetes-ingress-controller.bintray.io/kong-ingress-controller | | image.tag | Version of the ingress controller | 0.6.0 | @@ -398,3 +400,13 @@ You can can learn about kong ingress custom resource definitions [here](https:// | podDisruptionBudget.enabled | Enable PodDisruptionBudget for ingress controller | `false` | | podDisruptionBudget.maxUnavailable | Represents the minimum number of Pods that can be unavailable (integer or percentage) | `50%` | | podDisruptionBudget.minAvailable | Represents the number of Pods that must be available (integer or percentage) | | + + +## Changelog + +### 0.27.0 + +#### Breaking changes + +- DB-less mode is enabled by default. +- Kong is installed as an Ingress Controller for the cluster by default. diff --git a/stable/kong/values.yaml b/stable/kong/values.yaml index 4eae824ea4..71d0863db4 100644 --- a/stable/kong/values.yaml +++ b/stable/kong/values.yaml @@ -273,7 +273,7 @@ updateStrategy: {} # e.g. setting pg_user here will override the value normally set when postgresql.enabled # is set below. In general, you should not set values here if they are set elsewhere. env: - database: postgres + database: "off" nginx_worker_processes: "1" proxy_access_log: /dev/stdout admin_access_log: /dev/stdout @@ -359,11 +359,11 @@ podSecurityPolicy: # PostgreSQL chart configs postgresql: - enabled: true - postgresqlUsername: kong - postgresqlDatabase: kong - service: - port: 5432 + enabled: false + # postgresqlUsername: kong + # postgresqlDatabase: kong + # service: + # port: 5432 # Custom Kong plugins can be loaded into Kong by mounting the plugin code # into the file-system of Kong container. @@ -383,7 +383,7 @@ plugins: {} # created in k8s. It uses CRDs for more fine grained control over routing and # for Kong specific configuration. ingressController: - enabled: false + enabled: true image: repository: kong-docker-kubernetes-ingress-controller.bintray.io/kong-ingress-controller tag: 0.6.0