Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events, please visit our HCL Connections page.
Multiple helm charts use hardcoded ports for the service definition
When deploying multiple instances of the connections component pack on the same Kubernetes cluster in different namespaces, you find that several ports are hardcoded inside the helm charts. The provided helm charts must be modified by hand to change the node port inside the service description. The expectation is that I can configure the node port via a configuration file.
Kubernetes is a base technology and you should not expect that your product is the only component on the cluster. Expect that your product is just one component among many others on the same cluster.
Therefore: It is not just Connections in a different namespace is blocking the ports. There could be many other projects or some IT regularities that force that ports must be changed.
In the current customer setup, they decided to have 1 Kubernetes cluster for the test / quality environment and 1 for production. Therefore on the test / quality environment we currently have DEV 6.5, Quality 6.5 and DEV 7.0 running on 1 cluster and each of this infrastructures require a different namespace and a different node ports (as node ports as cluster global).