/ /

Arquitectura multiclúster sin malla de servicios

Docs Home

/ /

Arquitecturas de Referencia

Arquitectura multiclúster sin malla de servicios

Docs Home

Gestión

Controladores para el Operador de Kubernetes

Arquitecturas de Referencia

Arquitectura multiclúster sin malla de servicios

Implementar los controladores MongoDB para el operador Kubernetes sin una malla de servicios

Para implementar varias instancias de recursos de MongoDB en varios clústeres de Kubernetes, primero debe implementar el operador de Kubernetes en uno de sus clústeres. Una vez implementado el operador de Kubernetes en su clúster, podrá crear y administrar todos sus recursos de MongoDB en todos sus clústeres aplicando actualizaciones a dicho clúster.

Requisitos previos

Antes de comenzar el siguiente procedimiento, realice las siguientes acciones:

Instalar kubectl.
Instalar Helm.
Completar la Procedimiento de clústeres de GKE o equivalente.
Complete el procedimiento de Certificados TLS o equivalente.
Complete el procedimiento de malla de servicio Istio o equivalente.
Instalar el complemento kubectl mongodb. Para instalar el complemento kubectl mongodb:
1
Descargue la versión del paquete Kubernetes Operator que desee.
Descargue la versión del paquete Kubernetes Operator que desee desde la página de lanzamiento del repositorio de controladores MongoDB para operadores de Kubernetes.
El nombre del paquete utiliza este patrón: kubectl-mongodb_{{ .Version }}_{{ .Os }}_{{ .Arch }}.tar.gz.
Utilice uno de los siguientes paquetes:
kubectl-mongodb_{{ .Version }}_darwin_amd64.tar.gz
kubectl-mongodb_{{ .Version }}_darwin_arm64.tar.gz
kubectl-mongodb_{{ .Version }}_linux_amd64.tar.gz
kubectl-mongodb_{{ .Version }}_linux_arm64.tar.gz
2
Desempaquete el paquete del operador de Kubernetes.
Desempaquete el paquete, como en el siguiente ejemplo:
tar -zxvf kubectl-mongodb_<version>_darwin_amd64.tar.gz
3
Localice el kubectl mongodb binario del complemento y cópielo en su destino deseado.
Busque el binario kubectl-mongodb en el directorio descomprimido y muévalo a su destino deseado, dentro de PATH para el usuario Operador de Kubernetes, como se muestra en el siguiente ejemplo:
mv kubectl-mongodb /usr/local/bin/kubectl-mongodb
Ahora puedes ejecutar el complemento kubectl mongodb usando los siguientes comandos:
kubectl mongodb multicluster setup kubectl mongodb multicluster recover
Para obtener más información sobre los indicadores admitidos, consulte la Referencia del complemento kubectl de MongoDB.

Actualice según sea necesario y configure las variables de entorno definidas en el siguiente archivo env_variables.sh.

1 # Namespace in which Ops Manager and AppDB will be deployed
2 export OM_NAMESPACE="mongodb-om"
3 # Namespace in which the operator will be installed
4 export OPERATOR_NAMESPACE="mongodb-operator"
5 # Namespace in which MongoDB resources will be deployed
6 export MDB_NAMESPACE="mongodb"
7 
8 # comma-separated key=value pairs for additional parameters passed to the helm-chart installing the operator
9 export OPERATOR_ADDITIONAL_HELM_VALUES="${OPERATOR_ADDITIONAL_HELM_VALUES:-""}"
10 
11 export OFFICIAL_OPERATOR_HELM_CHART="mongodb/mongodb-kubernetes"
12 export OPERATOR_HELM_CHART="${OPERATOR_HELM_CHART:-${OFFICIAL_OPERATOR_HELM_CHART}}"

Código fuente

Puede encontrar todo el código fuente incluido en el repositorio del operador Kubernetes de MongoDB.

Procedimiento

Cree espacios de nombres para el operador de Kubernetes, MongoDB y Ops Manager en cada uno de sus clústeres de Kubernetes.

kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" create namespace "${OPERATOR_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_1_CONTEXT_NAME}" create namespace "${OPERATOR_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_2_CONTEXT_NAME}" create namespace "${OPERATOR_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" create namespace "${OM_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_1_CONTEXT_NAME}" create namespace "${OM_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_2_CONTEXT_NAME}" create namespace "${OM_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" create namespace "${MDB_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_1_CONTEXT_NAME}" create namespace "${MDB_NAMESPACE}"
kubectl --context "${K8S_CLUSTER_2_CONTEXT_NAME}" create namespace "${MDB_NAMESPACE}"

Crea secretos de imagen pull.

mkdir -p secrets
kubectl create secret generic "image-registries-secret" \
        --from-file=.dockerconfigjson="${HOME}/.docker/config.json" --type=kubernetes.io/dockerconfigjson \
        --dry-run=client -o yaml > secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OM_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_1_CONTEXT_NAME}" -n "${OM_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_2_CONTEXT_NAME}" -n "${OM_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${MDB_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_1_CONTEXT_NAME}" -n "${MDB_NAMESPACE}" apply -f secrets/image-registries-secret.yaml
kubectl --context "${K8S_CLUSTER_2_CONTEXT_NAME}" -n "${MDB_NAMESPACE}" apply -f secrets/image-registries-secret.yaml

Configure sus clústeres de Kubernetes.

Ejecute el siguiente comando para configurar sus clústeres de Kubernetes.

1 kubectl mongodb multicluster setup \
2   --central-cluster="${K8S_CLUSTER_0_CONTEXT_NAME}" \
3   --member-clusters="${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}" \
4   --member-cluster-namespace="${OM_NAMESPACE}" \
5   --central-cluster-namespace="${OPERATOR_NAMESPACE}" \
6   --create-service-account-secrets \
7   --install-database-roles=true \
8   --image-pull-secrets=image-registries-secret
9 
10 kubectl mongodb multicluster setup \
11   --central-cluster="${K8S_CLUSTER_0_CONTEXT_NAME}" \
12   --member-clusters="${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}" \
13   --member-cluster-namespace="${MDB_NAMESPACE}" \
14   --central-cluster-namespace="${OPERATOR_NAMESPACE}" \
15   --create-service-account-secrets \
16   --install-database-roles=true \
17   --image-pull-secrets=image-registries-secret

Build: 2c1990888c0e359896209c67e0430b7bda9f6922, 2025-12-12T15:47:45Z
Ensured namespaces exist in all clusters.
creating central cluster roles in cluster: gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrolebinding: mongodb-kubernetes-operator-mongodb-operator-multi-cluster-mongodb-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrolebinding: mongodb-kubernetes-operator-mongodb-operator-multi-cluster-mongodb-role-binding
creating member roles in cluster: gke_scratch-kubernetes-team_europe-central2-b_k8s-mdb-1-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
creating member roles in cluster: gke_scratch-kubernetes-team_europe-central2-c_k8s-mdb-2-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
Ensured ServiceAccounts and Roles.
Creating KubeConfig secret mongodb-operator/mongodb-enterprise-operator-multi-cluster-kubeconfig in cluster gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
Ensured database Roles in member clusters.
Creating Member list Configmap mongodb-operator/mongodb-kubernetes-operator-member-list in cluster gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
Build: 2c1990888c0e359896209c67e0430b7bda9f6922, 2025-12-12T15:47:45Z
Ensured namespaces exist in all clusters.
creating central cluster roles in cluster: gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrolebinding: mongodb-kubernetes-operator-mongodb-operator-multi-cluster-mongodb-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrolebinding: mongodb-kubernetes-operator-mongodb-operator-multi-cluster-mongodb-role-binding
creating member roles in cluster: gke_scratch-kubernetes-team_europe-central2-b_k8s-mdb-1-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
creating member roles in cluster: gke_scratch-kubernetes-team_europe-central2-c_k8s-mdb-2-69429168b45x2c95c2-13333
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
created clusterrole: mongodb-kubernetes-operator-multi-cluster-role-telemetry
created clusterrolebinding: mongodb-kubernetes-operator-multi-telemetry-cluster-role-binding
Ensured ServiceAccounts and Roles.
Creating KubeConfig secret mongodb-operator/mongodb-enterprise-operator-multi-cluster-kubeconfig in cluster gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
Secret mongodb-operator/mongodb-enterprise-operator-multi-cluster-kubeconfig already exists, updating it
Ensured database Roles in member clusters.
Creating Member list Configmap mongodb-operator/mongodb-kubernetes-operator-member-list in cluster gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333

Agregar MongoDB Helm Charts para Kubernetes.

Agregue el repositorio MongoDB Helm Charts para Kubernetes a Helm.

1 helm repo add mongodb https://mongodb.github.io/helm-charts
2 helm repo update mongodb
3 helm search repo "${OFFICIAL_OPERATOR_HELM_CHART}"

"mongodb" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "mongodb" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME                      	CHART VERSION	APP VERSION	DESCRIPTION                                       
mongodb/mongodb-kubernetes	1.6.1        	           	MongoDB Controllers for Kubernetes translate th...

Implementa el operador de Kubernetes.

Utilice los gráficos Helm de MongoDB para Kubernetes para implementar el operador de Kubernetes.

1 helm upgrade --install \
2   --debug \
3   --kube-context "${K8S_CLUSTER_0_CONTEXT_NAME}" \
4   mongodb-kubernetes-operator-multi-cluster \
5   "${OPERATOR_HELM_CHART}" \
6   --namespace="${OPERATOR_NAMESPACE}" \
7   --set namespace="${OPERATOR_NAMESPACE}" \
8   --set operator.namespace="${OPERATOR_NAMESPACE}" \
9   --set operator.watchNamespace="${OM_NAMESPACE}\,${MDB_NAMESPACE}" \
10   --set operator.name=mongodb-kubernetes-operator-multi-cluster \
11   --set operator.createOperatorServiceAccount=false \
12   --set operator.createResourcesServiceAccountsAndRoles=false \
13   --set "multiCluster.clusters={${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}}" \
14   --set "${OPERATOR_ADDITIONAL_HELM_VALUES:-"dummy=value"}" \
15   --set operator.env=dev

Release "mongodb-kubernetes-operator-multi-cluster" does not exist. Installing it now.
NAME: mongodb-kubernetes-operator-multi-cluster
LAST DEPLOYED: Wed Dec 17 11:29:05 2025
NAMESPACE: mongodb-operator
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
dummy: value
multiCluster:
  clusters:
  - gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
  - gke_scratch-kubernetes-team_europe-central2-b_k8s-mdb-1-69429168b45x2c95c2-13333
  - gke_scratch-kubernetes-team_europe-central2-c_k8s-mdb-2-69429168b45x2c95c2-13333
namespace: mongodb-operator
operator:
  createOperatorServiceAccount: false
  createResourcesServiceAccountsAndRoles: false
  env: dev
  name: mongodb-kubernetes-operator-multi-cluster
  namespace: mongodb-operator
  watchNamespace: mongodb-om,mongodb
COMPUTED VALUES:
agent:
  name: mongodb-agent
  version: 108.0.12.8846-1
community:
  agent:
    name: mongodb-agent
    version: 108.0.2.8729-1
  mongodb:
    imageType: ubi8
    name: mongodb-community-server
    repo: quay.io/mongodb
  registry:
    agent: quay.io/mongodb
  resource:
    members: 3
    name: mongodb-replica-set
    tls:
      caCertificateSecretRef: tls-ca-key-pair
      certManager:
        certDuration: 8760h
        renewCertBefore: 720h
      certificateKeySecretRef: tls-certificate
      enabled: false
      sampleX509User: false
      useCertManager: true
      useX509: false
    version: 4.4.0
database:
  name: mongodb-kubernetes-database
  version: 1.6.1
dummy: value
initAppDb:
  name: mongodb-kubernetes-init-appdb
  version: 1.6.1
initDatabase:
  name: mongodb-kubernetes-init-database
  version: 1.6.1
initOpsManager:
  name: mongodb-kubernetes-init-ops-manager
  version: 1.6.1
managedSecurityContext: false
mongodb:
  appdbAssumeOldFormat: false
  name: mongodb-enterprise-server
  repo: quay.io/mongodb
multiCluster:
  clusterClientTimeout: 10
  clusters:
  - gke_scratch-kubernetes-team_europe-central2-a_k8s-mdb-0-69429168b45x2c95c2-13333
  - gke_scratch-kubernetes-team_europe-central2-b_k8s-mdb-1-69429168b45x2c95c2-13333
  - gke_scratch-kubernetes-team_europe-central2-c_k8s-mdb-2-69429168b45x2c95c2-13333
  kubeConfigSecretName: mongodb-enterprise-operator-multi-cluster-kubeconfig
  performFailOver: true
namespace: mongodb-operator
operator:
  additionalArguments: []
  affinity: {}
  baseName: mongodb-kubernetes
  createOperatorServiceAccount: false
  createResourcesServiceAccountsAndRoles: false
  deployment_name: mongodb-kubernetes-operator
  enableClusterMongoDBRoles: true
  enablePVCResize: true
  env: dev
  maxConcurrentReconciles: 1
  mdbDefaultArchitecture: non-static
  name: mongodb-kubernetes-operator-multi-cluster
  namespace: mongodb-operator
  nodeSelector: {}
  operator_image_name: mongodb-kubernetes
  podSecurityContext:
    runAsNonRoot: true
    runAsUser: 2000
  replicas: 1
  resources:
    limits:
      cpu: 1100m
      memory: 1Gi
    requests:
      cpu: 500m
      memory: 200Mi
  securityContext: {}
  telemetry:
    collection:
      clusters: {}
      deployments: {}
      frequency: 1h
      operators: {}
    send:
      frequency: 168h
  tolerations: []
  vaultSecretBackend:
    enabled: false
    tlsSecretRef: ""
  version: 1.6.1
  watchNamespace: mongodb-om,mongodb
  watchedResources:
  - mongodb
  - opsmanagers
  - mongodbusers
  - mongodbcommunity
  - mongodbsearch
  webhook:
    installClusterRole: true
    registerConfiguration: true
opsManager:
  name: mongodb-enterprise-ops-manager-ubi
readinessProbe:
  name: mongodb-kubernetes-readinessprobe
  version: 1.0.23
registry:
  agent: quay.io/mongodb
  database: quay.io/mongodb
  imagePullSecrets: null
  initAppDb: quay.io/mongodb
  initDatabase: quay.io/mongodb
  initOpsManager: quay.io/mongodb
  operator: quay.io/mongodb
  opsManager: quay.io/mongodb
  pullPolicy: Always
  readinessProbe: quay.io/mongodb
  versionUpgradeHook: quay.io/mongodb
search:
  name: mongodb-search
  repo: quay.io/mongodb
  version: 0.55.0
versionUpgradeHook:
  name: mongodb-kubernetes-operator-version-upgrade-post-start-hook
  version: 1.0.10
HOOKS:
MANIFEST:
---
# Source: mongodb-kubernetes/templates/operator-roles-telemetry.yaml
# Additional ClusterRole for clusterVersionDetection
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: mongodb-kubernetes-operator-multi-cluster-cluster-telemetry
rules:
  # Non-resource URL permissions
  - nonResourceURLs:
      - "/version"
    verbs:
      - get
  # Cluster-scoped resource permissions
  - apiGroups:
      - ''
    resources:
      - namespaces
    resourceNames:
      - kube-system
    verbs:
      - get
  - apiGroups:
      - ''
    resources:
      - nodes
    verbs:
      - list
---
# Source: mongodb-kubernetes/templates/operator-roles-webhook.yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: mongodb-kubernetes-operator-multi-cluster-mongodb-operator-webhook-cr
rules:
  - apiGroups:
      - "admissionregistration.k8s.io"
    resources:
      - validatingwebhookconfigurations
    verbs:
      - get
      - create
      - update
      - delete
  - apiGroups:
      - ""
    resources:
      - services
    verbs:
      - get
      - list
      - watch
      - create
      - update
      - delete
---
# Source: mongodb-kubernetes/templates/operator-roles-telemetry.yaml
# ClusterRoleBinding for clusterVersionDetection
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: mongodb-kubernetes-operator-multi-cluster-mongodb-operator-cluster-telemetry-binding
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: mongodb-kubernetes-operator-multi-cluster-cluster-telemetry
subjects:
  - kind: ServiceAccount
    name: mongodb-kubernetes-operator-multi-cluster
    namespace: mongodb-operator
---
# Source: mongodb-kubernetes/templates/operator-roles-webhook.yaml
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: mongodb-kubernetes-operator-multi-cluster-mongodb-operator-webhook-crb
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: mongodb-kubernetes-operator-multi-cluster-mongodb-operator-webhook-cr
subjects:
  - kind: ServiceAccount
    name: mongodb-kubernetes-operator-multi-cluster
    namespace: mongodb-operator
---
# Source: mongodb-kubernetes/templates/operator.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mongodb-kubernetes-operator-multi-cluster
  namespace: mongodb-operator
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/component: controller
      app.kubernetes.io/name: mongodb-kubernetes-operator-multi-cluster
      app.kubernetes.io/instance: mongodb-kubernetes-operator-multi-cluster
  template:
    metadata:
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/name: mongodb-kubernetes-operator-multi-cluster
        app.kubernetes.io/instance: mongodb-kubernetes-operator-multi-cluster
    spec:
      serviceAccountName: mongodb-kubernetes-operator-multi-cluster
      securityContext:
        runAsNonRoot: true
        runAsUser: 2000
      containers:
        - name: mongodb-kubernetes-operator-multi-cluster
          image: "quay.io/mongodb/mongodb-kubernetes:1.6.1"
          imagePullPolicy: Always
          args:
            - -watch-resource=mongodb
            - -watch-resource=opsmanagers
            - -watch-resource=mongodbusers
            - -watch-resource=mongodbcommunity
            - -watch-resource=mongodbsearch
            - -watch-resource=mongodbmulticluster
            - -watch-resource=clustermongodbroles
          command:
            - /usr/local/bin/mongodb-kubernetes-operator
          volumeMounts:
            - mountPath: /etc/config/kubeconfig
              name: kube-config-volume
          resources:
            limits:
              cpu: 1100m
              memory: 1Gi
            requests:
              cpu: 500m
              memory: 200Mi
          env:
            - name: OPERATOR_ENV
              value: dev
            - name: MDB_DEFAULT_ARCHITECTURE
              value: non-static
            - name: NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: WATCH_NAMESPACE
              value: "mongodb-om,mongodb"
            - name: MDB_OPERATOR_TELEMETRY_COLLECTION_FREQUENCY
              value: "1h"
            - name: MDB_OPERATOR_TELEMETRY_SEND_FREQUENCY
              value: "168h"
            - name: CLUSTER_CLIENT_TIMEOUT
              value: "10"
            - name: IMAGE_PULL_POLICY
              value: Always
            # Database
            - name: MONGODB_ENTERPRISE_DATABASE_IMAGE
              value: quay.io/mongodb/mongodb-kubernetes-database
            - name: INIT_DATABASE_IMAGE_REPOSITORY
              value: quay.io/mongodb/mongodb-kubernetes-init-database
            - name: INIT_DATABASE_VERSION
              value: "1.6.1"
            - name: DATABASE_VERSION
              value: "1.6.1"
            # Ops Manager
            - name: OPS_MANAGER_IMAGE_REPOSITORY
              value: quay.io/mongodb/mongodb-enterprise-ops-manager-ubi
            - name: INIT_OPS_MANAGER_IMAGE_REPOSITORY
              value: quay.io/mongodb/mongodb-kubernetes-init-ops-manager
            - name: INIT_OPS_MANAGER_VERSION
              value: "1.6.1"
            # AppDB
            - name: INIT_APPDB_IMAGE_REPOSITORY
              value: quay.io/mongodb/mongodb-kubernetes-init-appdb
            - name: INIT_APPDB_VERSION
              value: "1.6.1"
            - name: OPS_MANAGER_IMAGE_PULL_POLICY
              value: Always
            - name: AGENT_IMAGE
              value: "quay.io/mongodb/mongodb-agent:108.0.12.8846-1"
            - name: MDB_AGENT_IMAGE_REPOSITORY
              value: "quay.io/mongodb/mongodb-agent"
            - name: MONGODB_IMAGE
              value: mongodb-enterprise-server
            - name: MONGODB_REPO_URL
              value: quay.io/mongodb
            - name: PERFORM_FAILOVER
              value: 'true'
            - name: MDB_MAX_CONCURRENT_RECONCILES
              value: "1"
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: OPERATOR_NAME
              value: mongodb-kubernetes-operator-multi-cluster
            # Community Env Vars Start
            - name: MDB_COMMUNITY_AGENT_IMAGE
              value: "quay.io/mongodb/mongodb-agent:108.0.2.8729-1"
            - name: VERSION_UPGRADE_HOOK_IMAGE
              value: "quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.10"
            - name: READINESS_PROBE_IMAGE
              value: "quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.23"
            - name: MDB_COMMUNITY_IMAGE
              value: "mongodb-community-server"
            - name: MDB_COMMUNITY_REPO_URL
              value: "quay.io/mongodb"
            - name: MDB_COMMUNITY_IMAGE_TYPE
              value: "ubi8"
            # Community Env Vars End
            - name: MDB_SEARCH_REPO_URL
              value: "quay.io/mongodb"
            - name: MDB_SEARCH_NAME
              value: "mongodb-search"
            - name: MDB_SEARCH_VERSION
              value: "0.55.0"
      volumes:
        - name: kube-config-volume
          secret:
            defaultMode: 420
            secretName: mongodb-enterprise-operator-multi-cluster-kubeconfig

Verifique el estado de sus controladores MongoDB para el operador Kubernetes.

1 kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" rollout status --timeout=2m deployment/mongodb-kubernetes-operator-multi-cluster
2 echo "Operator deployment in ${OPERATOR_NAMESPACE} namespace"
3 kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" get deployments
4 echo; echo "Operator pod in ${OPERATOR_NAMESPACE} namespace"
5 kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" get pods

Waiting for deployment "mongodb-kubernetes-operator-multi-cluster" rollout to finish: 0 of 1 updated replicas are available...
deployment "mongodb-kubernetes-operator-multi-cluster" successfully rolled out
Operator deployment in mongodb-operator namespace
NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
mongodb-kubernetes-operator-multi-cluster   1/1     1            1           7s
Operator pod in mongodb-operator namespace
NAME                                                       READY   STATUS    RESTARTS   AGE
mongodb-kubernetes-operator-multi-cluster-c7b4bc84-wlvcf   1/1     Running   0          8s

Volver

DNS externo

Certificados TLS

1	# Namespace in which Ops Manager and AppDB will be deployed
2	export OM_NAMESPACE="mongodb-om"
3	# Namespace in which the operator will be installed
4	export OPERATOR_NAMESPACE="mongodb-operator"
5	# Namespace in which MongoDB resources will be deployed
6	export MDB_NAMESPACE="mongodb"
7
8	# comma-separated key=value pairs for additional parameters passed to the helm-chart installing the operator
9	export OPERATOR_ADDITIONAL_HELM_VALUES="${OPERATOR_ADDITIONAL_HELM_VALUES:-""}"
10
11	export OFFICIAL_OPERATOR_HELM_CHART="mongodb/mongodb-kubernetes"
12	export OPERATOR_HELM_CHART="${OPERATOR_HELM_CHART:-${OFFICIAL_OPERATOR_HELM_CHART}}"

1	kubectl mongodb multicluster setup \
2	--central-cluster="${K8S_CLUSTER_0_CONTEXT_NAME}" \
3	--member-clusters="${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}" \
4	--member-cluster-namespace="${OM_NAMESPACE}" \
5	--central-cluster-namespace="${OPERATOR_NAMESPACE}" \
6	--create-service-account-secrets \
7	--install-database-roles=true \
8	--image-pull-secrets=image-registries-secret
9
10	kubectl mongodb multicluster setup \
11	--central-cluster="${K8S_CLUSTER_0_CONTEXT_NAME}" \
12	--member-clusters="${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}" \
13	--member-cluster-namespace="${MDB_NAMESPACE}" \
14	--central-cluster-namespace="${OPERATOR_NAMESPACE}" \
15	--create-service-account-secrets \
16	--install-database-roles=true \
17	--image-pull-secrets=image-registries-secret

1	helm repo add mongodb https://mongodb.github.io/helm-charts
2	helm repo update mongodb
3	helm search repo "${OFFICIAL_OPERATOR_HELM_CHART}"

1	helm upgrade --install \
2	--debug \
3	--kube-context "${K8S_CLUSTER_0_CONTEXT_NAME}" \
4	mongodb-kubernetes-operator-multi-cluster \
5	"${OPERATOR_HELM_CHART}" \
6	--namespace="${OPERATOR_NAMESPACE}" \
7	--set namespace="${OPERATOR_NAMESPACE}" \
8	--set operator.namespace="${OPERATOR_NAMESPACE}" \
9	--set operator.watchNamespace="${OM_NAMESPACE}\,${MDB_NAMESPACE}" \
10	--set operator.name=mongodb-kubernetes-operator-multi-cluster \
11	--set operator.createOperatorServiceAccount=false \
12	--set operator.createResourcesServiceAccountsAndRoles=false \
13	--set "multiCluster.clusters={${K8S_CLUSTER_0_CONTEXT_NAME},${K8S_CLUSTER_1_CONTEXT_NAME},${K8S_CLUSTER_2_CONTEXT_NAME}}" \
14	--set "${OPERATOR_ADDITIONAL_HELM_VALUES:-"dummy=value"}" \
15	--set operator.env=dev

1	kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" rollout status --timeout=2m deployment/mongodb-kubernetes-operator-multi-cluster
2	echo "Operator deployment in ${OPERATOR_NAMESPACE} namespace"
3	kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" get deployments
4	echo; echo "Operator pod in ${OPERATOR_NAMESPACE} namespace"
5	kubectl --context "${K8S_CLUSTER_0_CONTEXT_NAME}" -n "${OPERATOR_NAMESPACE}" get pods

Requisitos previos

Descargue la versión del paquete Kubernetes Operator que desee.

Desempaquete el paquete del operador de Kubernetes.

Localice el kubectl mongodb binario del complemento y cópielo en su destino deseado.

Código fuente

Procedimiento

Cree espacios de nombres para el operador de Kubernetes, MongoDB y Ops Manager en cada uno de sus clústeres de Kubernetes.

Crea secretos de imagen pull.

Configure sus clústeres de Kubernetes.

Agregar MongoDB Helm Charts para Kubernetes.

Implementa el operador de Kubernetes.

Verifique el estado de sus controladores MongoDB para el operador Kubernetes.

Localice el `kubectl mongodb` binario del complemento y cópielo en su destino deseado.