Connecting from Inside the cluster
OneDB Native SQLI connection are accessible through the OneDB Connection Manager. A
kubernetes service will be created with the deployment and that service name is used for
connections. A kubernetes service is created for the non-SQLI types as
well.
kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
helm-1-odbp-explore ClusterIP 10.96.220.30 <none> 8080/TCP 20m
helm-1-odbp-mongo ClusterIP 10.96.44.208 <none> 27017/TCP 20m
helm-1-odbp-rest ClusterIP 10.96.90.21 <none> 8080/TCP 20m
onedbcm-cm-service ClusterIP 10.96.159.103 <none> 10000/TCP,20000/TCP 19m
The OneDB Connection manager supports “Redirected” and “Proxied” connections. For internal connections it is recommended to use “Redirected” connections. The following table shows the Internal connection string to use for each driver type. From within the cluster the .{namespace}.svc.cluster.local may not be needed from the URL below.
| Driver | URL | Example URL |
| OneDB driver (SQLI-Primary) | onedbcm-cm-service.{namespace}.svc.cluster.local:10000 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Secondary) | onedbcm-cm-service.{namespace}.svc.cluster.local:10001 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Any) | onedbcm-cm-service.{namespace}.svc.cluster.local:10002 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Primary-SSL) | onedbcm-cm-service.{namespace}.svc.cluster.local:10020 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Secondary-SSL) | onedbcm-cm-service.{namespace}.svc.cluster.local:10021 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Any-SSL) | onedbcm-cm-service.{namespace}.svc.cluster.local:10022 | jdbc:onedb://{url}/sysmaster |
| Mongo combatible driver | <Release-Name>-odbp-mongo:27017 | mongodb://<release-name>-odbp-mongo:27017 |
| REST | <Release-Name>-odbp-rest:8080 | http://<release-name>-odbp-rest:8080 |
| Explore | <Release-Name>-odbp-explore:8080 | http://<release-name>-odbp-explore:8080 |