En este tema, se explica cómo especificar un espacio de nombres personalizado de Kubernetes para cert-manager.
En la mayoría de los casos, cert-manager se ejecuta en el espacio de nombres cert-manager. Algunos usuarios pueden tener políticas de la empresa que restrinjan la creación de espacios de nombres nuevos de Kubernetes o tener políticas que requieran que cert-manager se ejecute en un espacio de nombres diferente, por ejemplo, kube-system.
Especifica un espacio de nombres personalizado para cert-manager
Verifica que cert-manager se haya instalado de forma correcta en el espacio de nombres nuevo con el
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
Si cert-manager se ejecutaba antes, borra la instancia cert-manager en el espacio de nombres cert-manager mediante las instrucciones en Desinstalar en la documentación de cert-manager.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis documentation guides you through specifying a custom Kubernetes namespace for cert-manager, which typically runs in the \u003ccode\u003ecert-manager\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eYou may need to use a custom namespace due to company policies or specific requirements to run cert-manager in a different namespace, such as \u003ccode\u003ekube-system\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo install cert-manager in a custom namespace, you'll need to edit the installation manifests and add a \u003ccode\u003ecertManager\u003c/code\u003e stanza to your overrides file, specifying the new namespace.\u003c/p\u003e\n"],["\u003cp\u003eAfter installing, you can verify that cert-manager is running correctly in the new namespace by using the \u003ccode\u003ekubectl get pods\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIf cert-manager was installed in the \u003ccode\u003ecert-manager\u003c/code\u003e namespace previously, it should be uninstalled.\u003c/p\u003e\n"]]],[],null,["# Running cert-manager in a custom namespace\n\n| 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, 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.11/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:\n\n ### Helm\n\n Test with a dry run first: \n\n ```\n helm upgrade operator apigee-operator/ \\\n --install \\\n --namespace apigee-system \\\n --atomic \\\n -f OVERRIDES_FILE.yaml \\\n --dry-run\n ```\n\n Apply the change: \n\n ```\n helm upgrade operator apigee-operator/ \\\n --install \\\n --namespace apigee-system \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n ```\n\n ### `apigeectl`\n\n ```\n $APIGEECTL_HOME/apigeectl init -f OVERRIDES_FILE.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)."]]
