Neste tópico, explicamos como especificar um namespace personalizado do Kubernetes para o
cert-manager.
Na maioria dos casos, o cert-manager é executado no namespace cert-manager. Alguns usuários podem ter
políticas da empresa que restringem a criação de novos namespaces do Kubernetes ou algumas políticas que exigem
que o cert-manager seja executado em um namespace diferente, por exemplo, kube-system.
Especificar um namespace personalizado para o cert-manager
Aplique a mudança de namespace com apigeectl init:
apigeectl init -f path-to-overrides.yaml
Verifique se o cert-manager está instalado corretamente no novo namespace com o
comando kubectl get pods:
kubectl get pods -n new-cert-manager-namespace
NAME READY STATUS RESTARTS AGE
cert-manager-1234567-abcde 1/1 Running 0 21s
cert-manager-cainjector-23456789a-bcdef 1/1 Running 0 22s
cert-manager-webhook-3456789ab-cdef0 1/1 Running 0 20s
Se o cert-manager estava em execução anteriormente, exclua a instância de cert-manager no
namespace cert-manager seguindo as instruções em
Desinstalar
na documentação do cert-manager.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-28 UTC."],[[["\u003cp\u003eThis document guides you through configuring cert-manager to operate within a custom Kubernetes namespace instead of the default \u003ccode\u003ecert-manager\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eYou must manually create the desired namespace, such as \u003ccode\u003enew-cert-manager-namespace\u003c/code\u003e, before installing cert-manager.\u003c/p\u003e\n"],["\u003cp\u003eModifications to the cert-manager installation manifests are necessary to deploy it into a custom namespace as detailed in the linked documentation.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ecertManager\u003c/code\u003e stanza in your overrides file should be updated to include the desired namespace, and the changes should be applied using the \u003ccode\u003eapigeectl init\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIf cert-manager was previously running in the default namespace, you need to follow the cert-manager uninstallation steps before continuing.\u003c/p\u003e\n"]]],[],null,["# Running cert-manager in a custom namespace\n\n| You are currently viewing version 1.9 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis topic explains how to specify a custom Kubernetes namespace for\n[cert-manager](https://cert-manager.io/).\n\nIn most cases, cert-manager runs in the `cert-manager` namespace. Some users may have\ncompany policies restricting the creation of new Kubernetes namespaces or have policies requiring\ncert-manager to be run in a different namespace, for example `kube-system`.\n\n\nSpecify a custom namespace for cert-manager\n-------------------------------------------\n\n1. Create the namespace if needed: \n\n ```\n kubectl create namespace new-cert-manager-namespace\n ```\n2. Install cert-manager following the instructions in [Installation:\n Introduction](https://cert-manager.io/v1.10-docs/installation/) in the cert-manager documentation. **Note:** You will have to edit the installation manifests to install cert-manager in a custom namespace.\n3. Add a [`certManager`](/apigee/docs/hybrid/v1.9/config-prop-ref#certmanager) stanza to your overrides file. \n\n ```\n certManager:\n namespace: new-cert-manager-namespace\n \n ```\n4. Apply the namespace change with `apigeectl init`: \n\n ```\n apigeectl init -f path-to-overrides.yaml\n ```\n5. Verify that cert-manager installed correctly in the new namespace with the `kubectl get pods` command: \n\n ```\n kubectl get pods -n new-cert-manager-namespace\n ``` \n\n ```\n NAME READY STATUS RESTARTS AGE\n cert-manager-1234567-abcde 1/1 Running 0 21s\n cert-manager-cainjector-23456789a-bcdef 1/1 Running 0 22s\n cert-manager-webhook-3456789ab-cdef0 1/1 Running 0 20s\n ```\n6. If cert manager had previoiusly been running, delete the `cert-manager` instance in the `cert-manager` namespace by following the instructions in [Uninstall\n in the cert-manager documentation](https://cert-manager.io/docs/installation/kubectl/#uninstalling)."]]