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-27 UTC."],[[["This documentation guides you through specifying a custom Kubernetes namespace for cert-manager, which typically runs in the `cert-manager` namespace."],["Users 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."],["Installing cert-manager in a custom namespace involves creating the namespace, installing cert-manager using modified manifests, and adding a `certManager` stanza to the overrides file."],["After configuration, the `apigeectl init` command applies the namespace change, and `kubectl get pods` verifies the successful installation in the new namespace."],["If cert-manager was previously running, it needs to be uninstalled from the default `cert-manager` namespace before completing the process."]]],[]]