이 주제에서는 cert-manager의 커스텀 Kubernetes 네임스페이스를 지정하는 방법을 설명합니다.
대부분의 경우 cert-manager는 cert-manager 네임스페이스에서 실행됩니다. 일부 사용자는 새 Kubernetes 네임스페이스 생성을 제한하는 회사 정책을 가지고 있거나 다른 네임스페이스에서 cert-manager를 실행해야 하는 정책이 있을 수 있습니다(예: kube-system).
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(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\u003eUsers with company policies restricting new namespace creation or requiring cert-manager to run in a specific namespace can follow these steps to adjust the cert-manager's location.\u003c/p\u003e\n"],["\u003cp\u003eInstalling cert-manager in a custom namespace involves creating the namespace, installing cert-manager using modified manifests, and adding a \u003ccode\u003ecertManager\u003c/code\u003e stanza to the overrides file.\u003c/p\u003e\n"],["\u003cp\u003eAfter configuration, the \u003ccode\u003eapigeectl init\u003c/code\u003e command applies the namespace change, and \u003ccode\u003ekubectl get pods\u003c/code\u003e verifies the successful installation in the new namespace.\u003c/p\u003e\n"],["\u003cp\u003eIf cert-manager was previously running, it needs to be uninstalled from the default \u003ccode\u003ecert-manager\u003c/code\u003e namespace before completing the process.\u003c/p\u003e\n"]]],[],null,["# Running cert-manager in a custom namespace\n\n| You are currently viewing version 1.10 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.10/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)."]]
