Keep deployment patches in kustomization

Retain patch modifications in config/manager/kustomization.yaml
instead of removing them after bundle generation. This aligns with
the pattern used in the openstack-k8s-operators namespace.

The Makefile no longer removes the deployment patch, keeping the
kustomization file consistent with the generated bundle.

Implements request in this comment [1].

[1] #80 (comment)

Author: lpiwowar

Makefile

@@ -332,7 +332,6 @@ bundle: manifests kustomize operator-sdk ## Generate bundle manifests and metada
 	cd config/manager && $(KUSTOMIZE) edit add patch --kind Deployment --name controller-manager --patch "[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/env/0/value\", \"value\": \"$(OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION)\"}]"
 	$(KUSTOMIZE) build config/manifests | $(OPERATOR_SDK) generate bundle $(BUNDLE_GEN_FLAGS)
 	$(OPERATOR_SDK) bundle validate ./bundle
-	cd config/manager && $(KUSTOMIZE) edit remove patch --kind Deployment --name controller-manager --patch "[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/env/0/value\", \"value\": \"$(OPENSHIFT_LIGHTSPEED_OPERATOR_VERSION)\"}]"
 
 .PHONY: bundle-build
 bundle-build: ## Build the bundle image.

config/manager/kustomization.yaml

@@ -6,3 +6,9 @@ images:
 - name: controller
   newName: quay.io/openstack-lightspeed/operator
   newTag: latest
+patches:
+- patch: '[{"op": "replace", "path": "/spec/template/spec/containers/0/env/0/value",
+    "value": "latest"}]'
+  target:
+    kind: Deployment
+    name: controller-manager