kong-operator
kong-operator copied to clipboard
upmc-enterprises
manages kong clusters
I am trying to deploy kong operator but end up with error Error: required env POD_NAME not set, please configure downward API oc version oc v3.11.0+0cbc58b kubernetes v1.11.0+d4cacc0 features: Basic-Auth...
Need to run migrations as separate step which wasn't a requirement previously.
Need to allow users to specify additional annotations on the proxy service: **Example:** ``` metadata: name: kong-proxy annotations: service.beta.kubernetes.io/aws-load-balancer-ssl-cert: "arn:aws:iam::723765766667:server-certificate/certificate-name" service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "443" ```
To make the setup easier and also enforce better security, add a flag to force `https_only` on any api created or updated regardless of what's configured. This way we can...
There's an internal map which manages the clusters deployed inside the operator. Right now it's using the name of the cluster, need to make unique by appending the namespace or...
When generating consumers, credentials are not auto created, allow them to be and pass them off as secrets in a defined namespace so apps can auto consume. _NOTE: This is...