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 explains how to install and run cert-manager in a custom Kubernetes namespace instead of the default `cert-manager` namespace."],["Users might need to run cert-manager in a different namespace due to company policies or restrictions on creating new namespaces."],["The process involves creating the custom namespace, editing the installation manifests to specify the new namespace, and applying these changes via the overrides file."],["After applying the changes, you can verify the installation in the new namespace by using the `kubectl get pods` command, followed by deleting the original instance if needed."],["The documentation directs users to the official cert-manager documentation for installation and uninstallation instructions, if needed."]]],[]]