HCL Api Gateway for Connections

Posted by

HCL has added a new component, Apache Apisix Gateway.
See for example https://engage.ug/pages/session2026 session #adm02 “HCL Connections 2026: The Roadmap to Engagement, Collaboration, and an API-First Future”

Following the HCL instructions is straight forward. Unless you run multiple Componentpack (CP) instances in the same k8s cluster.

Challenges in our environment:
– We are using a central traefik instance since CP 6.5 on ports 31080 and 31443.
The default ports can’t be used. Each Apisix instance needs it’s own ports.

– we have a separate namespace for each CP instance.
Each Apisix instance will have it’s own namespace.
And it’s own ingress controllerName / ingressClass

– Installing the helm chart with the same release name is also a bad decission. Some global stuff depends on the name. Better:
helm install instance1-apisix apisix/apisix …
helm install instance2-apisix apisix/apisix …

Leave a Reply