Search: sharded cluster operator support by lsierant · Pull Request #816 · mongodb/mongodb-kubernetes

lsierant · 2026-02-20T10:46:03Z

Based on PR #806

Chain of upstream PRs as of 2026-03-03

PR Search Sharded+LoadBalancing: base feature branch #806:
master ← search/base
- PR Search: sharded cluster operator support #816 (THIS ONE):
  search/base ← search/sharded-cluster

Summary

MCK already supported deploying single instance of mongot process using MongoDBSearch resource, with the MongoDB replicaset as source. That meant the customers can run search queries/use search against a ReplicaSet deployment.
In this PR, we are adding support to have sharded cluster as source to the MongoDBSearch resource. So that search can be used with sharded clusters as well.

To achieve this we have added the new field in the ExternalMongoDBSource type that can be used to configure the details of the sharded cluster that is going to be used as source.

type ExternalMongoDBSource struct {
	// ShardedCluster contains configuration for external sharded MongoDB clusters.
	// Mutually exclusive with HostAndPorts.
	// +optional
	ShardedCluster *ExternalShardedClusterConfig `json:"shardedCluster,omitempty"`

The ExternalShardedClusterConfig is mainly used to generate the mongot config, so that mongot correctly knows how to talk to the mongod processes. Rest of the changes revolve around this.

Proof of Work

TBD

api/v1/search/mongodbsearch_types.go

controllers/operator/mongodbsearch_controller.go

api/v1/search/mongodbsearch_types.go

controllers/searchcontroller/mongodbsearch_reconcile_helper.go

controllers/operator/mongodbshardedcluster_controller.go

lsierant · 2026-02-20T13:08:03Z

controllers/operator/mongodbshardedcluster_controller.go

+	// Watch for MongoDBSearch resources that reference ShardedCluster MongoDB resources
+	// Only enqueue reconciliation requests for ShardedCluster resources, not ReplicaSet or Standalone
+	shardedKubeClient := mgr.GetClient()
+	err = c.Watch(source.Kind(mgr.GetCache(), &searchv1.MongoDBSearch{},


we have now two mechanisms for watching related resources. I'm wondering if we could align it with controllers/operator/watch/resource_watcher.go one way or another

controllers/operator/mongodbshardedcluster_controller.go

controllers/searchcontroller/enterprise_search_source_test.go

controllers/searchcontroller/mongodbsearch_reconcile_helper.go

controllers/searchcontroller/mongodbsearch_reconcile_helper_test.go

lsierant · 2026-02-20T13:54:10Z

controllers/searchcontroller/mongodbsearch_reconcile_helper_test.go

+	}
+}
+
+func TestValidatePerShardTLSSecretsAllExist(t *testing.T) {


we should have more tests testing full reconcile, checking all the expected resource names, mongot configs, etc.

those individual tests checking only validatePerShardTLSSecrets, validatePerShardTLSSecrets should be removed and covered in a bigger test case

lsierant · 2026-02-20T13:55:36Z

controllers/searchcontroller/search_construction.go

 }

+// CreateShardSearchStatefulSetFunc creates a StatefulSet for a specific shard's mongot deployment.
+func CreateShardSearchStatefulSetFunc(mdbSearch *searchv1.MongoDBSearch, shardedSource ShardedSearchSourceDBResource, shardIdx int, searchImage string) statefulset.Modification {


this should be unified with the replicaset mongot

controllers/searchcontroller/sharded_external_search_source_test.go

viveksinghggits · 2026-02-20T13:19:38Z

controllers/searchcontroller/mongodbsearch_reconcile_helper.go

+		return xerrors.Errorf("error creating/updating shard search service %v: %w", svcName, err)
+	}
+
+	zap.S().Debugf("Updated shard search service %v: %s", svcName, op)


we seem to be using zap.S().Debugf and log.Debugf , is that intentional? Should we just use one?

we should use log passed on the arguments. In practice it's the same thing, but zap.S() is just returning a top level default logger

Addressed
75e00dc

controllers/searchcontroller/mongodbsearch_reconcile_helper.go

controllers/operator/mongodbshardedcluster_controller.go

controllers/searchcontroller/search_construction.go

mongodb-community-operator/pkg/mongot/mongot_config.go

lsierant · 2026-02-23T20:39:20Z

evergreen retry

lsierant · 2026-02-23T20:39:33Z

evergreen refresh

# Based on PR #817 ## Chain of upstream PRs as of 2026-03-03 * PR #806: `master` ← `search/base` * PR #816: `search/base` ← `search/sharded-cluster` * PR #817: `search/sharded-cluster` ← `search/multiple-mongot` * **PR #853 (THIS ONE)**: `search/multiple-mongot` ← `search/lsierant/revert-rs-cluster-index`

Add sharded cluster support to the MongoDBSearch operator: - Per-shard mongot StatefulSet, Service, and ConfigMap resources - ShardedEnterpriseSearchSource for operator-managed sharded clusters - ShardedExternalSearchSource for external sharded MongoDB sources - Per-shard and shared TLS certificate handling (CertsSecretPrefix) - Sharded cluster controller applies per-shard mongod and mongos search config parameters pointing to internal shard-local mongot services - ReplicaSet controller skips search config for sharded clusters (handled by sharded controller instead) - ExternalShardedConfig/ExternalRouterConfig/ExternalShardConfig API types - CRD updated with sharded external source fields and per-shard TLS prefix

Missing e2e test for sharded search with one mongot instance

# Summary Addressing some of the review comments from the PR. ## Proof of Work  ## Checklist - [ ] Have you linked a jira ticket and/or is the ticket in the title? - [ ] Have you checked whether your jira ticket required DOCSP changes? - [ ] Have you added changelog file? - use `skip-changelog` label if not needed - refer to [Changelog files and Release Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes) section in CONTRIBUTING.md for more details

…loyment` (#832) # Summary  ## Proof of Work  ## Checklist - [ ] Have you linked a jira ticket and/or is the ticket in the title? - [ ] Have you checked whether your jira ticket required DOCSP changes? - [ ] Have you added changelog file? - use `skip-changelog` label if not needed - refer to [Changelog files and Release Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes) section in CONTRIBUTING.md for more details

…#834) ## Summary - Unify duplicate sharded vs non-sharded functions in the search controller into single parameterized versions - Extract shared config and service helpers (baseMongotConfig, mongotServicePorts, buildSearchSetParameters) - Fix missing owner references on non-sharded StatefulSet and Service (was already set on sharded path) ## Proof of Work Compiles, existing tests pass. Behavioral change is limited to adding `SetOwnerReference` on non-sharded resources (aligning with the sharded path). ## Checklist - [x] Have you linked a jira ticket and/or is the ticket in the title? - [x] Have you checked whether your jira ticket required DOCSP changes? - [x] Have you added changelog file? --------- Co-authored-by: Łukasz Sierant <lukasz.sierant@mongodb.com>

…le (#831)

# Based on PR #817 ## Chain of upstream PRs as of 2026-03-03 * PR #806: `master` ← `search/base` * PR #816: `search/base` ← `search/sharded-cluster` * PR #817: `search/sharded-cluster` ← `search/multiple-mongot` * **PR #853 (THIS ONE)**: `search/multiple-mongot` ← `search/lsierant/revert-rs-cluster-index`

This was referenced Feb 20, 2026

Search Sharded+LoadBalancing: base feature branch #806

Draft

Search Sharded+LoadBalancing: operator code changes and e2e #807

Closed

Search: e2e #808

Closed

Search Sharded+LoadBalancing: Code snippets for sharded mongo (internal+external) #809

Draft

lsierant force-pushed the search/sharded-cluster branch from ce459f2 to a917d32 Compare February 20, 2026 10:46

lsierant mentioned this pull request Feb 20, 2026

Search: support multiple mongots #817

Draft

3 tasks

lsierant force-pushed the search/sharded-cluster branch from a917d32 to 915b024 Compare February 20, 2026 10:52