Opening the ports from the Load Balancer service
In this deployment, most of the required ports are already opened from the NetBackup primary and media server load balancer services by default.
If you want to use a specific workload and that needs specific ports, you must add those ports in the port specification of the load balancer service.
In case of media server, you must add custom ports in the load balancer service of all the replicas. In case of scaling up the media server, user needs to explicitly add newly added custom ports in respective newly created load balancer services.
In case custom ports are added in the load balancer service and the same load balancer service is deleted or created again, you must add respective custom ports again in the load balancer service specification.
For all three scenarios, perform the steps given in this section.
To open the ports from the Load Balancer service
- Run the kubectl get service -n <namespace> command.
This command lists all the services available in given namespace.
- Edit the required primary or media load balancer service using kubectl edit service <service-name> -n <namespace> command.
For example:
For primary server load balancer service:
Service name starts with Name of primary server like <Name>-primary. Edit the service with the kubectl edit service <Name>-primary -n <namespace> command.
For media server load balancer service:
Each replica of media server has its own load balancer service with name <Name>-media-<ordinal number>. For example, replica 2 of media server has a load balancer service with name <Name>-media-1.
You must modify service for specific replica with the kubectl edit service <Name>-media-<replica-ordinal number> -n <namespace> command.
Note:
The load balancer service with name Name used in primary sever and media server specification must be unique.
- Add entry for new port in ports array in specification field of the service. For example, if user want to add 111 port, then add the following entry in ports array in specification field.
name: custom-111 port: 111 protocol: TCP targetPort: 111 - Save the changes.
The service is updated and the new port is listed in ports list of the respective service when you run the kubectl get service -n <namespace> command.