Pods

onedb-operator

The purpose of the operator pod is to manager the OneDB HA cluster. By default, a OneDB HA Cluster is started with an HDR primary and secondary server, along with two connection managers.

onedb-server-x

This is the OneDB Database server pod. When deployed, a statefulset is used which will be assigned an ordinal index starting with 0. So, OneDB HA cluster with a primary secondary will have onedb-server-0 and onedb-server-1.

onedbcm-x

This is the OneDB Connection manager pod. It will be assigned an ordinal index starting with 0. By default, 2 connection managers are started. onedbcm-0 and onedbcm-1.

odbp-mongo

This is the OneDB Mongo Listener pod. It is started when the OneDB Mongo chart is deployed. It is used to connect to the OneDB Database server using the Mongo API.

odbp-rest

This is the OneDB REST Listener pod. It is started when the OneDB REST chart is deployed. It is used to connect to the OneDB Database esrver using RESTFUL services.

odbp-explore

This is the OneDB Explore pod. It will deploy the OneDB Explore administration and monitoring tool providing a web admin and monitoring GUI. It can be used to administer one or more OneDB Database servers.