SWAT within containerised (Viya4) environments : Referring to the bin and http K8s services

On a Viya 4 environment, I have published the sas-cas-server-default-bin and ..default-http services as NodePorts. A conscious decision has been taken to not deploy them as LoadBalancers in order to reduce entry points and administration overhead.

Accessing a Python editor from within SAS Studio (which is the customer's intended use), I am able to successfully connect to the binary service, through the controller's (internal) IP address - a sequence starting with 10.XX.XX.XX

Services in K8s are commonly accessed through the DNS name of <service_name>.<name_of_name_space>.svc.cluster.local. In this case, however, I am unable to connect through any of the following patterns (including port of 5570).

Within the connection string of

conn=swat.CAS(hostname=, port=, user=, password=)

hostname = any of the following :

sas-cas-server-default-bin.viya.svc.cluster.local
cas-shared-default-bin.viya.svc.cluster.local
sas-cas-server-default-controller.viya.svc.cluster.local

What might be the correct naming convention so that I do not have to have my users explicitly state the IP ?

Start by reproducing the connection attempts from Python inside SAS Studio and compare the listed Kubernetes service names and port 5570 with the services published in the Viya environment. Check the Kubernetes service DNS and NodePort configuration to determine the supported hostname, then confirm that the resulting connection avoids requiring users to enter an internal IP.