Hi Kong Nation!
We have Kong EE running and are running into a little manageability problem.
When deploying Kong Ingress Controller, and pointing it at a Kong EE installation, it will add all Ingress definitions into the default workspace.
We have different tenants, and need to separate them by workspace.
Currently, if you want to push a certain ingress resource to a certain workspace, you have to deploy a separate kong-ingress-controller, override the ingress class with
--ingress-class= and then override the workspace name with
Then if you want an ingress to be part of workspace a you have to add an annotation on the Ingress resource for
This does not scale when using this for many teams.
We had an idea of possibly using another annotation on the Ingress resource, to specify the workspace it needs to be pushed to such as:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: some-ingress annotations: workspace.konghq.com: XXX # Here we can specify the workspace name for where this ingress should be registered in Kong EE spec: ...
This would remove the need to run multiple ingress controllers for different workspaces.
In normal circumstance without the annotation, push to the default workspace, and with the ingress controller being workspace aware, if it finds the annotation, just push to that workspace.
Any feedback or ideas ?