In diesem Thema wird erläutert, wie Sie einen benutzerdefinierten Kubernetes-Namespace für cert-manager angeben.
In den meisten Fällen wird cert-manager im Namespace cert-manager ausgeführt. Einige Nutzer haben möglicherweise Unternehmensrichtlinien, die die Erstellung neuer Kubernetes-Namespaces einschränken oder cert-manager in einem anderen Namespace ausführen müssen. Beispiel: kube-system.
Benutzerdefinierten Namespace für cert-manager angeben
Prüfen Sie mit dem Befehl kubectl get pods, ob cert-manager im neuen Namespace korrekt installiert wurde:
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
Wenn cert-manager bereits ausgeführt wurde, löschen Sie die cert-manager-Instanz im cert-manager-Namespace. Folgen Sie dazu der Anleitung unter Deinstallieren in der cert-manager-Dokumentation. eine
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-21 (UTC)."],[[["\u003cp\u003eThis guide details the process of installing and running cert-manager in a custom Kubernetes namespace, diverging from the default \u003ccode\u003ecert-manager\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eUsers can define a custom namespace for cert-manager using \u003ccode\u003ekubectl\u003c/code\u003e to create it and then modifying the installation manifests and the overrides file, instead of using the default namespace.\u003c/p\u003e\n"],["\u003cp\u003eThe installation process involves editing the manifests, adding a \u003ccode\u003ecertManager\u003c/code\u003e stanza to the overrides file with the desired namespace, and then using \u003ccode\u003ehelm\u003c/code\u003e to apply the changes.\u003c/p\u003e\n"],["\u003cp\u003eAfter installation, it is essential to verify that cert-manager is running correctly in the new namespace by checking the pod status with \u003ccode\u003ekubectl get pods\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf a previous instance of cert-manager existed, users will need to delete it from the default \u003ccode\u003ecert-manager\u003c/code\u003e namespace before installing in the new namespace.\u003c/p\u003e\n"]]],[],null,["# Running cert-manager in a custom namespace\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. 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.14/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: Test with a dry run first:\n\n ```\n helm upgrade operator apigee-operator/ \\\n --install \\\n --namespace APIGEE_NAMESPACE \\\n --atomic \\\n -f OVERRIDES_FILE.yaml \\\n --dry-run=server\n ```\n\n Apply the change: \n\n ```\n helm upgrade operator apigee-operator/ \\\n --install \\\n --namespace APIGEE_NAMESPACE \\\n --atomic \\\n -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)."]]
