マルチクラスターシャードクラスタ

1  shardPodSpec: # applicable to all shards in all clusters2    persistence:3      single:4        storage: "5G"5    podTemplate:6      spec:7        containers:8          - name: mongodb-enterprise-database9            resources:10              requests:11                cpu: 0.512                memory: 1.0G13              limits:14                cpu: 1.015                memory: 2.0G16  shard:17    clusterSpecList:18      - clusterName: kind-e2e-cluster-119        members: 220        # The below statefulset override is applicable only to pods in kind-e2e-cluster-121        # Specs will be merged, the "request" field defined above will still be22        # applied to containers in this cluster.23        # However, limits will be replaced with below values, because24        # clusterSpecList.statefulSet.spec.template has a25        # higher priority than shardPodSpec.podTemplate26        statefulSet:27          spec:28            template:29              spec:30                containers:31                  - name: mongodb-enterprise-database32                    resources:33                      limits:34                        cpu: 1.035                        memory: 2.5G36        # In clusterSpecList.podSpec, only persistence field must be used, the37        # podTemplate field is ignored.38        # In kind-e2e-cluster-1, we replace the persistence settings defined in39        # shardPodSpec40        podSpec:41          persistence:42            multiple:43              journal:44                storage: "6G"45              data:46                storage: "7G"47              logs:48                storage: "6G"49      - clusterName: kind-e2e-cluster-250        members: 1

1        # In clusterSpecList.podSpec, only persistence field must be used, the2        # podTemplate field is ignored.3        # In kind-e2e-cluster-1, we define custom persistence settings4        podSpec:5          persistence:6            multiple:7              journal:8                storage: "5G"9              data:10                storage: "5G"11              logs:12                storage: "5G"13      - clusterName: kind-e2e-cluster-214        members: 115
16  shardOverrides:17    - shardNames: [ "pod-template-shards-1-2" ]18      # This override will apply to shard of index 219      # Statefulset settings defined at this level (shardOverrides.statefulSet)20      # apply to members of shard 2 in ALL clusters.21      # This field has higher priority than shard.clusterSpecList.statefulSet, but22      # lower than shardOverrides.clusterSpecList.statefulSet23      # It has a merge policy, which means that the limits defined above for the24      # mongodb-enterprise-database container field still apply to all members in25      # that shard, except if overridden.26      statefulSet:27        spec:28          template:29            spec:30              containers:31                - name: sidecar-shard-232                  image: busybox33                  command: [ "sleep" ]34                  args: [ "infinity" ]35      clusterSpecList:36        - clusterName: kind-e2e-cluster-137          members: 238        - clusterName: kind-e2e-cluster-239          members: 140          # The below statefulset override is applicable only to members of shard 2, in cluster 141          # Specs will be merged, the "limits" field defined above will still be applied42          # to containers in this cluster together with the requests field below.43          statefulSet:44            spec:45              template:46                spec:47                  containers:48                    - name: mongodb-enterprise-database49                      resources:50                        requests: # We add a requests field in shard 2, cluster 151                          cpu: 0.552                          memory: 1.0G53
54          podSpec:55            # In shardOverrides.clusterSpecList.podSpec, only persistence field must be56            # used, the podTemplate field is ignored.57            persistence: # we assign additional disk resources in shard 2, cluster 158              multiple:59                journal:60                  storage: "6G"61                data:62                  storage: "6G"63                logs:64                  storage: "6G"

1# This file is an example of how to migrate from the old deprecated2# ShardSpecificPodSpec field to the new shardOverrides fields3# for single cluster deployments.4# The settings specified in shardOverrides are the exact equivalent to the5# ones in shardSpecificPodSpec, showing how to replicate them6apiVersion: mongodb.com/v17kind: MongoDB8metadata:9  name: shardspecificpodspec-migration10  namespace: mongodb-test11spec:12  # There are 4 shards in this cluster, but the shardSpecificPodSpec field13  # doesn't need to have on entry per shard, it can have less14  shardCount: 415  mongodsPerShardCount: 216  mongosCount: 117  configServerCount: 318  topology: SingleCluster19  type: ShardedCluster20  version: 8.0.321  opsManager:22    configMapRef:23      name: my-project24  credentials: my-credentials25  persistent: true26
27  shardPodSpec:28    # default persistence configuration for all shards in all clusters29    persistence:30      single:31        storage: "5G"32  shardSpecificPodSpec: # deprecated way of overriding shards (array)33    - persistence: # shard of index 034        single:35          storage: "6G"36      # Specify resources settings to enterprise database container in shard 037      podTemplate:38        spec:39          containers:40            - name: mongodb-enterprise-database41              resources:42                requests:43                  cpu: 0.544                  memory: 1G45                limits:46                  cpu: 1.047                  memory: 2.0G48    - persistence: # shard of index 149        single:50          storage: "7G"51    - persistence: # shard of index 252        single:53          storage: "7G"54
55  # The below shardOverrides replicate the same shards configuration as the one56  # specified above in shardSpecificPodSpec57  shardOverrides:58    - shardNames: [ "shardspecificpodspec-migration-0" ] # overriding shard #059      podSpec:60        persistence:61          single:62            storage: "6G"63      statefulSet:64        spec:65          template:66            spec:67              containers:68                - name: mongodb-enterprise-database69                  resources:70                    requests:71                      cpu: 0.572                      memory: 1G73                    limits:74                      cpu: 1.075                      memory: 2.0G76
77    # The ShardSpecificPodSpec field above has the same configuration for shards78    # 1 and 2. It is possible to specify both shard names in the override and not79    # duplicate that configuration80    - shardNames: [ "shardspecificpodspec-migration-1", "shardspecificpodspec-migration-2" ]81      podSpec:82        persistence:83          single:84            storage: "7G"