From 2370e654772ca92d17f0f3a8d60f8f7577822995 Mon Sep 17 00:00:00 2001
From: Mikalai Radchuk <509198+m1kola@users.noreply.github.com>
Date: Fri, 18 Jul 2025 18:10:43 +0200
Subject: [PATCH] Fix OLM install modes

Currently with OLM we claim to support `OwnNamespace`, `SingleNamespace`,
and `AllNamespaces` install modes.

However, only `OwnNamespace` works properly when deploying OpsManager.
With other install modes, the operator is able to reconcile resources
and create `StatefulSets` for the workloads in OpsManager,
but pods never become healthy because only the operator's own namespace
has the required `ServiceAccount`.

With this change, we make the relevant `ServiceAccount`
managed by OLM. This means the `ServiceAccount` and relevant roles
will be created in all required namespaces.
---
 Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Makefile b/Makefile
index 9c45c1c3b..bd3641046 100644
--- a/Makefile
+++ b/Makefile
@@ -388,6 +388,7 @@ bundle: manifests kustomize
 	operator-sdk generate kustomize manifests -q
 	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)\
 		--channels=stable --default-channel=stable\
+		--extra-service-accounts mongodb-kubernetes-appdb \
 		--output-dir ./bundle/$(VERSION)/
 	operator-sdk bundle validate ./bundle/$(VERSION)