You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Signing Jobs can be created in any namespace, while the ConfigMaps containing the OpenShift CA
certificates from the bundle are only present in the operator's namespace.
In each namespace containing a Module or targeted by a ManagedClusterModule, create two ConfigMaps
for each CA certificate type. Those ConfigMaps are populated by other OpenShift controllers.
When creating a signing Job, look for those ConfigMaps in the Job's namespace and mount them
accordingly.
Set the ConfigMaps owner references appropriately so that they are deleted when all Modules /
ManagedClusterModules that might need it are deleted.
deploy: manifests kustomize ## Deploy controller to the K8s cluster specified in ~/.kube/config.
199
200
cd config/manager &&$(KUSTOMIZE) edit set image controller=$(IMG)
200
201
oc apply -k $(KUSTOMIZE_CONFIG_DEFAULT)
201
202
203
+
.PHONY: deploy-hub
204
+
deploy-hub: manifests kustomize ## Deploy controller to the K8s cluster specified in ~/.kube/config.
205
+
cd config/manager-hub &&$(KUSTOMIZE) edit set image controller=$(HUB_IMG)
206
+
oc apply -k $(KUSTOMIZE_CONFIG_HUB_DEFAULT)
207
+
202
208
.PHONY: undeploy
203
209
undeploy: ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
undeploy-hub: ## Undeploy controller from the K8s cluster specified in ~/.kube/config. Call with ignore-not-found=true to ignore resource not found errors during deletion.
0 commit comments