Kong(Cluster)Plugins do not work anymore after upgrade to Ingress Controller 0.10.0

Kubernetes
1

The previously configured plugins work perfectly under 0.9.1.

 {
  "plugins": {
    "enabled_in_cluster": [
    "correlation-id",
    "acme",
    "post-function",
    "ip-restriction",
    "response-transformer"
    ]
   }
 }

After upgrading to 0.10.0 only one plugin is still configured.

{
  "plugins": {
    "enabled_in_cluster": [
      "correlation-id"
    ]
  }
}

Reverting back to 0.9.1 makes the plugin active again.

Example configuration of correlation-id (the one that still works).

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: myapp-request
  namespace: mynamespace
  labels:
    global: "true"
disabled: false
config:
  header_name: myapp-request-id
  generator: uuid
plugin: correlation-id

Example of a plugin, that doesn’t work anymore.

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: myapp-cors
  labels:
    global: "true"
config:
  origins:
    - https://mycoolappwhatever.com
plugin: cors

Log:

time="2020-09-27T10:22:09Z" level=info msg="no configuration change, skipping sync to kong" component=controller

Any thoughts?

Thanks!

2

Please add in the kubernetes.io/ingress.class: kong annotation to the KongClusterPlugin reource.
This is one of the breaking changes that shipped in 0.10.

Changelog: https://github.com/Kong/kubernetes-ingress-controller/blob/main/CHANGELOG.md

1 Like