f7edd01e49
```
Updated:
argo/argo-cd:
- 5.52.1
bitnami/airflow:
- 16.1.11
bitnami/cassandra:
- 10.6.9
bitnami/kafka:
- 26.6.3
bitnami/mariadb:
- 15.0.1
bitnami/mysql:
- 9.16.1
bitnami/postgresql:
- 13.2.29
bitnami/redis:
- 18.6.3
bitnami/spark:
- 8.1.8
bitnami/tomcat:
- 10.11.11
bitnami/wordpress:
- 19.0.5
bitnami/zookeeper:
- 12.4.4
cert-manager/cert-manager:
- v1.13.3
clastix/kamaji:
- 0.14.0
cockroach-labs/cockroachdb:
- 11.2.3
confluent/confluent-for-kubernetes:
- 0.824.40
crowdstrike/falcon-sensor:
- 1.24.1
datadog/datadog:
- 3.50.5
datadog/datadog-operator:
- 1.4.1
dell/csi-isilon:
- 2.9.0
dell/csi-powermax:
- 2.9.0
dell/csi-powerstore:
- 2.9.0
dell/csi-unity:
- 2.9.0
dell/csi-vxflexos:
- 2.9.0
digitalis/vals-operator:
- 0.7.8
dynatrace/dynatrace-operator:
- 0.15.0
external-secrets/external-secrets:
- 0.9.11
f5/nginx-ingress:
- 1.1.0
fairwinds/polaris:
- 5.17.0
gluu/gluu:
- 5.0.24
haproxy/haproxy:
- 1.35.5
harbor/harbor:
- 1.14.0
hashicorp/consul:
- 1.3.1
instana/instana-agent:
- 1.2.66
intel/intel-device-plugins-operator:
- 0.29.0
intel/intel-device-plugins-qat:
- 0.29.0
intel/intel-device-plugins-sgx:
- 0.29.0
jenkins/jenkins:
- 4.11.2
jfrog/artifactory-ha:
- 107.71.11
jfrog/artifactory-jcr:
- 107.71.11
kong/kong:
- 2.33.3
kubecost/cost-analyzer:
- 1.108.1
kuma/kuma:
- 2.5.1
linkerd/linkerd-control-plane:
- 1.16.9
mongodb/community-operator:
- 0.9.0
nats/nats:
- 1.1.6
new-relic/nri-bundle:
- 5.0.58
nutanix/nutanix-csi-snapshot:
- 6.3.2
nutanix/nutanix-csi-storage:
- 2.6.6
openebs/openebs:
- 3.10.0
percona/psmdb-db:
- 1.15.1
percona/pxc-db:
- 1.13.4
redpanda/redpanda:
- 5.7.7
speedscale/speedscale-operator:
- 2.0.2
stackstate/stackstate-k8s-agent:
- 1.0.66
sysdig/sysdig:
- 1.16.24
traefik/traefik:
- 26.0.0
trilio/k8s-triliovault-operator:
- 4.0.0
weka/csi-wekafsplugin:
- 2.3.2
yugabyte/yugabyte:
- 2.18.5
yugabyte/yugaware:
- 2.18.5
```
|
||
|---|---|---|
| .. | ||
| charts/community-operator-crds | ||
| templates | ||
| Chart.lock | ||
| Chart.yaml | ||
| README.md | ||
| values.yaml | ||
README.md
MongoDB Community Kubernetes Operator Helm Chart
A Helm Chart for installing and upgrading the MongoDB Community Kubernetes Operator.
Prerequisites
If required, you can install the Custom Resource Definitions Helm Chart separately or as a dependency of this Chart.
If the community-operator-crds Helm chart has been installed already, or if you
don't want to install the CRDs (because you have already installed them), then
you need to pass --set community-operator-crds.enabled=false, when
installing the Operator.
Installing Community Operator
You can install the MongoDB Community Operator easily with:
helm install community-operator mongodb/community-operator
This will install CRDs and Community Operator in the current namespace
(default by default). You can pass a different namespace with:
helm install community-operator mongodb/community-operator --namespace mongodb [--create-namespace]
To install the Community Operator in a namespace called mongodb with the
optional --create-namespace in case mongodb didn't exist yet.
Deploying a MongoDB Replica Set
The Community Operator will be watching for resources of type
mongodbcommunity.mongodbcommunity.mongodb.com; you can quickly install
a sample Mongo Database with:
kubectl apply -f https://raw.githubusercontent.com/mongodb/mongodb-kubernetes-operator/master/config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml [--namespace mongodb]
- Note: Make sure you add the
--namespaceoption when needed. - Note 2: A new user will be created with a generic password. Make sure this is only used for testing purposes.
After a few minutes you will have a 3-member MongoDB Replica Set installed in your cluster, that you can check with:
$ kubectl get mdbc
NAME PHASE VERSION
example-mongodb Running 4.2.6
Connecting to MongoDB from a Client Application
The Operator will create a Secret object, per user, created as part of the
deployment of the MongoDB resource. Each Secret will contain a Connection
String that can be mounted into a client application to connect to this MongoDB
instance.
The name of this Secret object follows the convention1:
<mongodb-resource-name>-<database>-<username>.
In our example, the above kubectl apply command will create a MongoDB resource
with name example-mongodb, with a user my-user on the Database admin. The
resulting Secret will be named:
example-mongodb-admin-my-user
This Secret object will contain the following attributes:
connectionString.standardconnectionString.standardSrvusernamepassword
A client application will be able to connect using the connectionString
attributes or the username and password ones.