Connecting from Outside 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 LoadBalancer 10.96.220.30 172.19.255.202 8080/TCP 20m
helm-1-odbp-mongo LoadBalancer 10.96.44.208 172.19.255.201 27017/TCP 20m
helm-1-odbp-rest LoadBalancer 10.96.90.21 172.19.255.200 8080/TCP 20m
onedbcm-cm-service LoadBalancer 10.96.159.103 172.19.255.203 10000/TCP,20000/TCP 19m
The OneDB Connection manager supports “Redirected” and “Proxied” connections. For external connections you must use the “Proxied” connections. The following table shows the external connection string to use for each driver type.
| Driver | URL | Example URL |
| OneDB driver (SQLI-Primary) | {LoadBalancer External IP address}:20000 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Secondary) | {LoadBalancer External IP address}:20001 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Any) | {LoadBalancer External IP address}:20002 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Primary-SSL) | {LoadBalancer External IP address}:20020 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Secondary-SSL) | {LoadBalancer External IP address}:20021 | jdbc:onedb://{url}/sysmaster |
| OneDB driver (SQLI-Any-SSL) | {LoadBalancer External IP address}:20022 | jdbc:onedb://{url}/sysmaster |
| Mongo combatible driver | {LoadBalancer External IP address}:27017 | mongodb://{url}:27017 |
| REST | {LoadBalancer External IP address}:8080 | http://{url}:8080 |
| Explore | {LoadBalancer External IP address}:8080 | http://{url}:8080 |