Configuring additional ports
Only the application UI ports are open for external access on the services and/or ingress routes, by default, when you deploy Certified Container on a container management platform. You can open additional ports for external access for adapters and other integration points through configurations available for ASI, AC and API application container deployments.
To open an additional ports, you need to configure it in the Helm configuration file
values.yaml) or through the Platform UI.
- Add a port mapping for internal pod access for the application deployment (ASI, AC or
For example: asi: extraPorts: -name: <internal-port-name> ## my-http-adapter port: <internal-port-number> ## 35000 targetPort: <internal-port-name> ## my-http-adapter protocol: TCP
- Add a port mapping for external access to the service and/or ingress routes for the applicable
application deployment (ASI, AC or
For example: ac: service: extraPorts: -name: http-1 port: <service-port-number> ## Can be same as internal port number (35000) or different say 45000. targetPort: <internal-port-name> ## my-http-adapter nodePort: <node-port-number> ## Required only if service type in use is NodePort. Should be in the range 30000-32767. protocol: TCPNote: In case of an HTTP endpoint, for service type
LoadBalancer, the external access URL is:
http<or https>://<service public ip>:<service-port-number>/<target uri>
Open the additional ports in container platform
- Helm upgrade: Add the port number in the
extra portsand save the changes.Run
helm upgrade -f <values.yaml> <name of the Helm release> <path to upadated helm charts>
- Port Forward: Use the command line for port forward option available in container platforms.
For more information, see
Kubernetes: Port Forwarding to Access Applications in a Cluster
Openshift: Port Forwarding.
Verify the opened ports
>Kubectl get service <service name> - Kubernetes cluster >oc service <service name> - OpenShift setup