Closed xiaoronglv closed 3 months ago
@czeslavo
Could you please take a look when you get the time?
when installing the kong though helm, how to specify the gateway-api-controller-name
?
@xiaoronglv when using the ingress
chart you should be able to do that via
gateway:
proxy:
... my values
controller:
ingressController:
env:
gateway_api_controller_name: name
@xiaoronglv I'm going to close this one. If there's still something you'd like us to look at, don't hesitate to write.
Thank you, @pmalek !
Your solutions works really well!
Hi Kong Engineers,
Good day!
I would like to deploy two Kong Gateway Instances to an AWS Kubernetes Cluster (EKS):
Install the first Kong Gateway Instance
Kong provides excellent documentation on how to install the Kong Ingress Controller using Helm. The deployment of my public API gateway was very smooth.
Here is the values.yaml file used:
Here is the command to install the public API gateway:
After installation, I defined the GatewayClass with the default controllerName konghq.com/kic-gateway-controller:
Everything works fine
Install second Kong Gateway Instance
After installing the public kong gateway, I started to install the second kong gateway instance as the internal API gateway instance. I need to specify a new
controllerName: konghq.com/kic-gateway-controller-private
. Then I could reference the controllerName when define the GatewayClass for internal purpose.However, I couldn't find any values.yaml example in the codebase that illustrates how to customize the controllerName for the gateway class, which is crucial for deploying multiple Kong gateway instances.
The documentation "Using Custom Classes to split Internal/External traffic" seems stale and the parameter
controller.ingressController.ingressClass
recommend by the documentation seems not working.Question
How to customize the controllerName of GatwayClass in the values.yaml when using the
kong ingress controller
chart?could you please provide a values.yaml example in this examples folder?
Thank you!
Reference