Skip to content
|
Kong Ingress Controller
3.1.x
github-edit-pageEdit this page
report-issueReport an issue
You are browsing documentation for an older version. See the latest documentation here.

Workspaces

Kong Ingress Controller can manage configuration in multiple workspaces when running in DB-backed mode. Each workspace needs a different Kong Ingress Controller instance with the --watch-namespace and --kong-workspace flags set.

  • --watch-namespace: Namespace(s) to watch for Kubernetes resources. Defaults to all namespaces. To watch multiple namespaces, use a comma-separated list of namespaces.
  • --kong-workspace: Kong Enterprise workspace to configure. Leave this empty if not using Kong workspaces.

Use this values.yaml when you install Kong Ingress Controller using Helm to configure the namespace and workspace.

gateway:
  ingressController:
    env:
      watch_namespace: mynamespacehere
      kong_workspace: workspacename

Kong Ingress Controller watches for resources in the defined namespace and send them to the configured workspace. This allows teams to manage their own resources in Kubernetes and send them to their own workspace within Kong Gateway.