Configuring external access for application backend (non-HTTP) endpoints
You can access the application backend or non-HTTP endpoints, configured primarily for services and adapters, through the backend service.
You need to configure one of the below options:
- Enable and configure LoadBalancer of the cloud provider by setting the service type to LoadBalancer.
- Using node IP and node port by setting the service type to NodePort. Note: Using the NodePort service is not recommended, particularly for production environments.
The backend service configurations are available for the following deployment services:
asi backend service
– Maps to the asi deployment pods.ac backend service
– Maps to the ac deployment pods.
Configurations:
asi.backendService.type/ac.backendService.type
- Set to a valid external service type Load Balancer or Node Port.Note: Using the NodePort service is not recommended, particularly for production environments.asi.backendService.ports/ac.backendService.ports
- configure external ports as individual port mappings with the following port configuration options invalues.yaml
:- name: name for the port mapping.
- port: service port number.
- targetPort: target pod port name or number.
- nodePort: service node port number. Applicable only for service type node port.
- protocol: valid protocol for the container environment. Defaults to TCP.
asi.backendService.portRanges/ac.backendService.portRanges
- configure external ports as port range mappings with the following port range configuration options invalues.yaml
:- name: name for the port range mapping.
- portRange: service port number range.
- targetPortRange: target pod port number range.
- nodePortRange: service node port number range. Applicable only for service type node port.
- protocol: valid protocol for the container environment. Defaults to TCP