I am migrating kong deployment from ECS to Kubernetes and deploying kong using the Kubernetes guide of kong.
I have the following use case
What steps would be required to deploy KONG with Postgres in EKS(for testing purpose). We are taking the configuration dynamically from the service provider, so the static configuration of service/rout/plugin will not work. Here Actually I am confused about the first step . I have referred the doc but about the k8 cluster and prerequisite ot sure.
The second case is after POC, our Kubernetes is being managed by our sysops team and they have created multiple namespaces for multiple teams. I have only admin access of particular namespace, I went through the documentation of kong how to deploy and observed it is needed cluster level access for creating the few resources.
My current deployment based on ECS ALB->Target Group–>ECS
i. we have exposed management API internally to do dynamic configuration(create service, route,
consumer, upstream and apply plugin), NO static configuration only configuration through MGMT
ii. Serving Proxy Traffic in other ports and exposed to the external world.
Please suggest me, what needs to be done to achieve the same deployment group in EKS.
I have a question can I deploy kong in a namespace level successfully to handle for production traffic