Topik ini menjelaskan cara menentukan namespace Kubernetes kustom untuk
cert-manager.
Pada umumnya, cert-manager berjalan di namespace cert-manager. Beberapa pengguna mungkin memiliki kebijakan perusahaan yang membatasi pembuatan namespace Kubernetes baru atau memiliki kebijakan yang mewajibkan cert-manager dijalankan di namespace yang berbeda, misalnya kube-system.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-03-12 UTC."],[[["This guide details the process of installing cert-manager in a custom Kubernetes namespace, deviating from the default `cert-manager` namespace."],["To install cert-manager in a custom namespace, you need to create the namespace, modify the installation manifests, and configure the `certManager` stanza in your overrides file."],["The process requires using `helm upgrade` commands with your modified overrides file to apply the namespace change, after testing with a dry run first."],["Verification of the installation in the custom namespace is achieved using the `kubectl get pods` command with the designated namespace."],["If cert-manager was already running in the default namespace, it must be uninstalled following the official cert-manager uninstallation guide after setting up the custom namespace."]]],[]]