Set up services/routes in helm chart in DB mode

Jared_Bischof · June 1, 2020, 4:38pm

I am running kong in kubernetes using the helm chart and connecting to a postgres DB. However, I noticed that (according to the comments) I am not supposed to use the services or routes sections in the values.yaml file if I am not running in DB-less mode. What is the suggested approach for initializing services and routes when running in DB mode? I would prefer to initialize these in the helm chart if possible.

github.com

Kong/charts/blob/6e815ca79e62eaa776c4f79a888e83e7e3ac05d7/charts/kong/values.yaml#L234


  preUpgrade: true
  # Enable post-upgrade migrations (run "kong migrations finish")
  postUpgrade: true
  # Annotations to apply to migrations jobs
  # By default, these disable service mesh sidecar injection for Istio and Kuma,
  # as the sidecar containers do not terminate and prevent the jobs from completing
  annotations:
    sidecar.istio.io/inject: false
    kuma.io/sidecar-injection: "disabled"

# Kong's configuration for DB-less mode
# Note: Use this section only if you are deploying Kong in DB-less mode
# and not as an Ingress Controller.
dblessConfig:
  # Either Kong's configuration is managed from an existing ConfigMap (with Key: kong.yml)
  configMap: ""
  # Or the configuration is passed in full-text below
  config:
    _format_version: "1.1"
    services:
      # Example configuration

github.com

Kong/charts/blob/6e815ca79e62eaa776c4f79a888e83e7e3ac05d7/charts/kong/values.yaml#L234


  preUpgrade: true
  # Enable post-upgrade migrations (run "kong migrations finish")
  postUpgrade: true
  # Annotations to apply to migrations jobs
  # By default, these disable service mesh sidecar injection for Istio and Kuma,
  # as the sidecar containers do not terminate and prevent the jobs from completing
  annotations:
    sidecar.istio.io/inject: false
    kuma.io/sidecar-injection: "disabled"

# Kong's configuration for DB-less mode
# Note: Use this section only if you are deploying Kong in DB-less mode
# and not as an Ingress Controller.
dblessConfig:
  # Either Kong's configuration is managed from an existing ConfigMap (with Key: kong.yml)
  configMap: ""
  # Or the configuration is passed in full-text below
  config:
    _format_version: "1.1"
    services:
      # Example configuration

hbagdi · June 1, 2020, 11:01pm

If you are using in the ingress controller mode, you should use Ingress resource to initialize.
If you using Kong stand-alone, you can use Admin API or decK to configure this.

Jared_Bischof · June 1, 2020, 11:34pm

Thanks for the response @hbagdi! Could you point me to documentation or an example of how to use the Ingress resource to initialize services/routes?

hbagdi · June 3, 2020, 3:59pm

https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/guides/getting-started.md should help you somewhat, although it doesn’t provide what you are looking for out of the box.

Topic		Replies	Views
Helm install Kong creating postgresql container and services in DB less mode Questions	10	1332	January 23, 2020
Kong Helm Chart and External Postgres database Kubernetes	23	10944	November 8, 2023
Very little documentation for DB version of Kong with Kubernetes Kubernetes	4	1092	September 23, 2021
Declarative config, services/routes only Questions	2	576	April 18, 2019
DBless and Kong Ingress Controller Kubernetes	5	1486	January 4, 2020

Set up services/routes in helm chart in DB mode

Related Topics