Connect to the IrisCluster

Connect to the IrisCluster

The serviceTemplate field creates one or more Kubernetes servicesOpens in a new tab to expose the IrisCluster to the network through external IP addresses. For example, a service is always created for the first pod in the first stateful set managing data nodes, which represents data node 1 in a sharded cluster, the data server in a distributed cache cluster, or a stand-alone instance, and is used to connect to the InterSystems IRIS instance running on that node for web applications, application connections, data ingestion and other purposes. You can connect to the superserver port (1972) by default, and to the web server port (80) if you included a webgateway sidecar in your data node definition. (If you deployed the sidecar from a webgateway-lockeddown imageOpens in a new tab, the web server port is 52773.) To get the IP address for the node, list the services representing the IrisCluster, as follows:

$ kubectl get svc 
NAME                       TYPE          CLUSTER-IP   EXTERNAL-IP     PORT(S)                         AGE
my-IrisCluster             LoadBalancer  10.35.245.6  35.196.145.234  1972:30011/TCP,80:31887/TCP     46m
my-IrisCluster-Webgateway  LoadBalancer  10.35.245.9  35.196.145.177  80:31887/TCP                    46m

You can then make connections to the node at the displayed external IP address, as illustrated in the following:

• To open the cluster’s Management PortalOpens in a new tab in your browser, use the following URL:

  http://external-ip:80/csp/sys/UtilHome.csp
  

  

• You can use a similar URL to interact with any of the built-in web applications on the first data node. For example, for the InterSystems Public Key InfrastructureOpens in a new tab you would use

  http://external-ip:80/isc/pki/PKI.CAServer.cls
  

  

• To make connections to the superserver port of InterSystems IRIS on the first data node, use external-ip:1972. For example, when connecting through the JDBC driver to load data into a sharded clusterOpens in a new tab, or for relational data access from a Java applicationOpens in a new tab, you would form the JDBC connection stringOpens in a new tab as follows:

  jdbc:IRIS://external-ip:1972/namespace
  

  

If you opened additional ports using the ports field in your serviceTemplate definitions, these will be available as well.

You can also define a similar serviceOpens in a new tab for the pod representing any other data or compute node if you wish to access its Management Portal or another web application through its webgateway sidecar, or to connect to its superserver port or any additional open ports you specified using the ports field.

Other services and external IP addresses created by default, if the applicable nodes are included in the IrisCluster, represent the first pod in the first stateful set managing webgateway nodes, sam nodes, and iam nodes. The URLs (including ports) for these connections are as follows: