You are currently viewing version 1.11 of the Apigee hybrid documentation.This version is end of life. You should upgrade to a newer version. For more information, seeSupported versions.

This topic explains how to specify a custom Kubernetes namespace forcert-manager.

In most cases, cert-manager runs in thecert-manager namespace. Some users may have company policies restricting the creation of new Kubernetes namespaces or have policies requiring cert-manager to be run in a different namespace, for examplekube-system.

Specify a custom namespace for cert-manager

1. Create the namespace if needed:

   kubectl create namespacenew-cert-manager-namespace

2. Install cert-manager following the instructions inInstallation: Introduction in the cert-manager documentation.Note: You will have to edit the installation manifests to install cert-manager in a custom namespace.
3. Add acertManager stanza to your overrides file.

   certManager:  namespace:new-cert-manager-namespace

4. Apply the namespace change:

   Helm

   Test with a dry run first:

   helm upgrade operator apigee-operator/ \  --install \  --namespace apigee-system \  --atomic \  -fOVERRIDES_FILE.yaml \  --dry-run

   Apply the change:

   helm upgrade operator apigee-operator/ \  --install \  --namespace apigee-system \  --atomic \  -fOVERRIDES_FILE.yaml

   apigeectl

   $APIGEECTL_HOME/apigeectl init -fOVERRIDES_FILE.yaml

5. Verify that cert-manager installed correctly in the new namespace with thekubectl get pods command:

   kubectl get pods -nnew-cert-manager-namespace

   NAME                                      READY   STATUS    RESTARTS   AGEcert-manager-1234567-abcde                1/1     Running   0          21scert-manager-cainjector-23456789a-bcdef   1/1     Running   0          22scert-manager-webhook-3456789ab-cdef0      1/1     Running   0          20s

6. If cert manager had previoiusly been running, delete thecert-manager instance in thecert-manager namespace by following the instructions inUninstall in the cert-manager documentation.