{"id":4748,"date":"2026-09-18T10:00:00","date_gmt":"2026-09-18T03:00:00","guid":{"rendered":"https:\/\/rna.id\/blog\/?p=4748"},"modified":"2026-05-22T11:01:22","modified_gmt":"2026-05-22T04:01:22","slug":"cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager","status":"publish","type":"post","link":"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/","title":{"rendered":"Cara Setup Multi-Domain SSL di Kubernetes (Ingress + Cert Manager)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Mengelola banyak domain dalam satu cluster Kubernetes bisa jadi mimpi buruk jika <a href=\"https:\/\/rna.id\/blog\/apa-itu-ssl-pengertian-fungsi-jenis-cara-mendapatkannya\/\">sertifikat SSL<\/a> harus diurus satu per satu secara manual. Belum lagi risiko sertifikat expired yang bisa <a href=\"https:\/\/rna.id\/blog\/panduan-membuat-website\/\">membuat website<\/a> tidak aman. Kabar baiknya, ada cara untuk mengatasi kendala tersebut, yakni dengan menggabungkan NGINX Ingress Controller dan Cert-Manager.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Metode ini bekerja dengan cara mengotomasi penerbitan dan pembaruan SSL multi domain di Kubernetes. Cukup konfigurasi sekali, semua domain di cluster akan terlindungi secara otomatis. Artikel ini akan memberikan panduan cara untuk setup multi domain di Kubernetes dengan metode Ingress + Cert-Manager. Langsung saja, yuk kita bahas!<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_90 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Daftar Isi<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #212529;color:#212529\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #212529;color:#212529\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#Mengenal_Multi-Domain_SSL_di_Kubernetes\" >Mengenal Multi-Domain SSL di Kubernetes<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#1_Peran_Ingress_Controller\" >1. Peran Ingress Controller<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#2_Peran_Cert-Manager\" >2. Peran Cert-Manager<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#Syarat_untuk_Setup_Multi-Domain_SSL_di_Kubernetes\" >Syarat untuk Setup Multi-Domain SSL di Kubernetes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#Cara_Setup_Multi-Domain_SSL_di_Kubernetes_Ingress_Cert_Manager\" >Cara Setup Multi-Domain SSL di Kubernetes (Ingress + Cert Manager)<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#1_Install_NGINX_Ingress_Controller\" >1. Install NGINX Ingress Controller<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#2_Install_Cert-Manager\" >2. Install Cert-Manager<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#3_Buat_Cluster_Issuer_Lets_Encrypt\" >3. Buat Cluster Issuer Let&#8217;s Encrypt<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#4_Konfigurasi_Ingress_Multi-Domain_dengan_SSL\" >4. Konfigurasi Ingress Multi-Domain dengan SSL<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#5_Verifikasi_Sertifikat_SSL_Aktif\" >5. Verifikasi Sertifikat SSL Aktif<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#Tips_Troubleshooting_Umum\" >Tips &amp; Troubleshooting Umum<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#1_Challenge_Stuck_di_Status_Pending\" >1. Challenge Stuck di Status Pending<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#2_Sertifikat_Tidak_Diterbitkan_Setelah_Beberapa_Menit\" >2. Sertifikat Tidak Diterbitkan Setelah Beberapa Menit<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#3_Terkena_Rate_Limit_Lets_Encrypt\" >3. Terkena Rate Limit Let&#8217;s Encrypt<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#4_Secret_Name_Konflik_Antar_Domain\" >4. Secret Name Konflik Antar Domain<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#5_Ingress_Class_Tidak_Cocok\" >5. Ingress Class Tidak Cocok<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/rna.id\/blog\/cara-setup-multi-domain-ssl-di-kubernetes-ingress-cert-manager\/#Kesimpulan\" >Kesimpulan<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Mengenal_Multi-Domain_SSL_di_Kubernetes\"><\/span>Mengenal Multi-Domain SSL di Kubernetes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sebelum masuk ke pembahasan teknis, penting untuk memahami dua komponen utama yang bekerja di balik setup ini:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Peran_Ingress_Controller\"><\/span>1. Peran Ingress Controller<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ingress adalah Kubernetes resource yang mengelola akses eksternal ke layanan dalam cluster, biasanya untuk trafik HTTP dan <a href=\"https:\/\/rna.id\/blog\/https-adalah\/\">HTTPS<\/a>. Dengan Ingress, kamu bisa mengelola routing rules yang kompleks, mengamankan aplikasi dengan <a href=\"https:\/\/rna.id\/blog\/perbedaan-ssl-vs-tls\/\">SSL\/TLS<\/a>, serta melakukan konsolidasi akses ke banyak layanan di balik satu external <a href=\"https:\/\/rna.id\/blog\/ip-address-adalah\/\">IP address<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sederhananya, Ingress adalah &#8220;pintu gerbang&#8221; yang mengatur semua trafik dari luar masuk ke dalam cluster. Setiap domain yang menuju cluster akan diarahkan ke service yang tepat berdasarkan rules yang kamu definisikan.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Peran_Cert-Manager\"><\/span>2. Peran Cert-Manager<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Cert-Manager adalah native Kubernetes certificate management controller yang dapat membantu menerbitkan sertifikat dari berbagai sumber. Cert menyediakan <a href=\"https:\/\/rna.id\/blog\/certificate-authority\/\">certificate authority<\/a> dari Let&#8217;s Encrypt, HashiCorp Vault, Venafi, hingga self-signed certificate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pada prakteknya, Cert-Manager mengelola siklus hidup sertifikat secara otomatis. Certificate bisa diminta dan dikonfigurasi hanya dengan menambahkan anotasi pada Ingress resource tanpa perlu intervensi secara manual.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Syarat_untuk_Setup_Multi-Domain_SSL_di_Kubernetes\"><\/span>Syarat untuk Setup Multi-Domain SSL di Kubernetes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Sebelum mulai setup multi domain di Kubernetes, pastikan semua prasyarat berikut sudah terpenuhi agar prosesnya berjalan lancar tanpa hambatan:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Kubernetes cluster aktif<\/strong> versi 1.21 atau lebih baru, dengan kubectl sudah terkonfigurasi dan terhubung ke cluster kamu.<\/li>\n\n\n\n<li><strong>Helm terinstall<\/strong> di local machine sebagai package manager untuk instalasi Ingress controller dan cert-manager.<\/li>\n\n\n\n<li><strong>Domain aktif<\/strong> yang sudah terdaftar dan dapat kamu kelola DNS record-nya secara penuh.<\/li>\n\n\n\n<li><strong>A record DNS<\/strong> untuk setiap domain sudah diarahkan ke external IP cluster Kubernetes kamu.<\/li>\n\n\n\n<li><strong>Akses internet publik<\/strong> ke cluster, karena Let&#8217;s Encrypt membutuhkan akses dari luar untuk proses validasi domain via HTTP-01 challenge.<\/li>\n\n\n\n<li><strong>Email aktif<\/strong> untuk didaftarkan ke Let&#8217;s Encrypt sebagai kontak notifikasi sertifikat.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Cara_Setup_Multi-Domain_SSL_di_Kubernetes_Ingress_Cert_Manager\"><\/span>Cara Setup Multi-Domain SSL di Kubernetes (Ingress + Cert Manager)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Setelah semua persyaratan terpenuhi, sekarang mari kita masuk ke praktek. Langsung saja, berikut cara untuk setup multi domain SSL di Kubernetes menggunakan metode Ingress dan Cert-Manager:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Install_NGINX_Ingress_Controller\"><\/span>1. Install NGINX Ingress Controller<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Langkah pertama adalah menginstall NGINX Ingress Controller sebagai entry point semua trafik HTTP dan <a href=\"https:\/\/rna.id\/blog\/https-adalah\/\">HTTPS<\/a> yang masuk ke cluster. Install via Helm dengan perintah berikut:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm repo add ingress-nginx https:\/\/kubernetes.github.io\/ingress-nginx<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm repo update<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm install ingress-nginx ingress-nginx\/ingress-nginx \\<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211;namespace ingress-nginx &#8211;create-namespace<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Setelah selesai, cek apakah pod sudah berjalan dan ambil external IP dari Load Balancer:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl get pods -n ingress-nginx<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl get svc -n ingress-nginx<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Catat external IP yang muncul dari Load Balancer service. Arahkan DNS A record setiap domain kamu ke IP ini \u2014 baik app1.example.com maupun app2.example.com semuanya mengarah ke satu IP Ingress yang sama.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Install_Cert-Manager\"><\/span>2. Install Cert-Manager<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Cert-Manager bertugas mengotomasi penerbitan dan pembaruan TLS certificate dari Let&#8217;s Encrypt. Cert-Manager akan terintegrasi dengan Ingress controller seperti NGINX untuk menangani certificate management secara otomatis. Untuk menginstalnya, kamu bisa menggunakan Helm:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm repo add jetstack https:\/\/charts.jetstack.io<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm repo update<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>helm install cert-manager jetstack\/cert-manager \\<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211;namespace cert-manager &#8211;create-namespace \\<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211;version v1.14.1 \\<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211;set installCRDs=true<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pastikan tiga pod berikut sudah berstatus Running:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl get pods -n cert-manager<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pod yang diharapkan akan muncul:<em> <\/em><strong><em>cert-manager<\/em><\/strong>, <strong><em>cert-manager-cainjector<\/em><\/strong>, dan <strong><em>cert-manager-webhook<\/em><\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Buat_Cluster_Issuer_Lets_Encrypt\"><\/span>3. Buat Cluster Issuer Let&#8217;s Encrypt<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Cluster Issuer mendefinisikan dari mana cert-manager akan meminta sertifikat. Gunakan Cluster Issuer agar bisa dipakai di seluruh namespace cluster tanpa konfigurasi ulang. Let&#8217;s Encrypt memiliki rate limit yang ketat, jadi gunakan staging issuer dahulu untuk pengujian, baru ke production setelah konfigurasi benar. Silakan buat file <strong><em>cluster-issuer.yaml<\/em><\/strong>:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>apiVersion: cert-manager.io\/v1<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kind: ClusterIssuer<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>metadata:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;name: letsencrypt-prod<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>spec:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;acme:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;server: https:\/\/acme-v02.api.letsencrypt.org\/directory<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;email: your-email@example.com<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;privateKeySecretRef:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: letsencrypt-prod<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;solvers:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&#8211; http01:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ingress:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;class: nginx<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ganti<em> <\/em><strong><em>your-email@example.com<\/em><\/strong> dengan email aktif kamu, lalu apply:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl apply -f cluster-issuer.yaml<\/em><\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Konfigurasi_Ingress_Multi-Domain_dengan_SSL\"><\/span>4. Konfigurasi Ingress Multi-Domain dengan SSL<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ini adalah inti dari cara setup multi domain di Kubernetes. Satu Ingress resource bisa menangani beberapa domain sekaligus, masing-masing mendapat sertifikat SSL tersendiri secara otomatis. Silakan buat file<strong><em> multi-domain-ingress.yaml<\/em><\/strong>:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>apiVersion: networking.k8s.io\/v1<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kind: Ingress<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>metadata:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;name: multi-host-ingress<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;namespace: production<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;annotations:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;cert-manager.io\/cluster-issuer: &#8220;letsencrypt-prod&#8221;<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;nginx.ingress.kubernetes.io\/force-ssl-redirect: &#8220;true&#8221;<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>spec:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;ingressClassName: nginx<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;tls:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211; hosts:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&#8211; app1.example.com<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;secretName: app1-tls<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211; hosts:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&#8211; app2.example.com<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;secretName: app2-tls<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;rules:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211; host: app1.example.com<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;http:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;paths:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#8211; path: \/<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pathType: Prefix<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;backend:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;service:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: app1-service<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;number: 80<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&#8211; host: app2.example.com<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;http:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;paths:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#8211; path: \/<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pathType: Prefix<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;backend:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;service:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;name: app2-service<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;port:<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;number: 80<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Setiap domain akan mendapatkan sertifikat dan secret tersendiri. Pastikan setiap entri tls memiliki secretName yang unik agar tidak terjadi konflik antar sertifikat domain. Perhatikan dua anotasi penting di bagian <strong><em>metadata<\/em><\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><em>cert-manager.io\/cluster-issuer <\/em><\/strong>\u2014 menghubungkan Ingress ke ClusterIssuer yang sudah dibuat sebelumnya.<\/li>\n\n\n\n<li><strong><em>nginx.ingress.kubernetes.io\/force-ssl-redirect<\/em><\/strong> \u2014 memaksa semua traffic HTTP dialihkan otomatis ke HTTPS.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Apply konfigurasi:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl apply -f multi-domain-ingress.yaml<\/em><\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Verifikasi_Sertifikat_SSL_Aktif\"><\/span>5. Verifikasi Sertifikat SSL Aktif<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Setelah Ingress ter-apply, cert-manager langsung memulai proses permintaan sertifikat ke Let&#8217;s Encrypt. Proses ini biasanya selesai dalam 1\u20133 menit. Pantau statusnya dengan:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl describe certificate app1-tls -n production<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl describe certificate app2-tls -n production<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cek juga proses challenge berjalan:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><em>kubectl get challenges -n production<\/em><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sertifikat dinyatakan aktif ketika status menunjukkan <strong><em>Ready: True<\/em><\/strong> dan tidak ada challenge yang tersisa dalam kondisi pending. Buka domain di browser \u2014 ikon gembok di address bar adalah konfirmasi bahwa SSL Kubernetes multi domain kamu sudah berjalan sempurna.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Tips_Troubleshooting_Umum\"><\/span>Tips &amp; Troubleshooting Umum<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Meskipun cara setup multi domain di Kubernetes terlihat simpel, tapi bisa saja tidak berjalan mulus di percobaan pertama. Berikut masalah yang sering muncul beserta solusinya.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Challenge_Stuck_di_Status_Pending\"><\/span>1. Challenge Stuck di Status Pending<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ini adalah bentuk error paling umum yang terjadi saat proses validasi Let&#8217;s Encrypt tidak bisa diselesaikan. Penyebab utamanya hampir selalu soal <a href=\"https:\/\/rna.id\/blog\/apa-itu-dns-kenali-fungsi-cara-kerja-dan-jenisnya\/\">DNS (Domain Name System)<\/a> atau di akses jaringan. Yang perlu kamu cek antara lain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pastikan A record setiap domain sudah benar-benar mengarah ke external IP Ingress controller kamu.<\/li>\n\n\n\n<li>Verifikasi cluster bisa diakses dari internet publik via port 80 \u2014 Let&#8217;s Encrypt wajib bisa menjangkau domain kamu untuk HTTP-01 challenge.<\/li>\n\n\n\n<li>Cek detail error dengan perintah kubectl describe challenge -n production untuk melihat pesan error spesifiknya.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Sertifikat_Tidak_Diterbitkan_Setelah_Beberapa_Menit\"><\/span>2. Sertifikat Tidak Diterbitkan Setelah Beberapa Menit<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Kalau setelah 5\u201310 menit sertifikat masih belum Ready: True, kemungkinan ada masalah di level Cluster Issuer atau anotasi Ingress. Yang perlu kamu cek antara lain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pastikan anotasi <strong><em>cert-manager.io\/cluster-issuer<\/em><\/strong> di Ingress sudah mengarah ke nama Cluster Issuer yang benar.<\/li>\n\n\n\n<li>Jika menggunakan ClusterIssuer, pastikan anotasi yang digunakan adalah <strong><em>cert-manager.io\/cluster-issuer<\/em><\/strong> \u2014 bukan c<strong><em>ert-manager.io\/issuer <\/em><\/strong>\u2014 agar sertifikat bisa diterbitkan lintas namespace tanpa kendala.<\/li>\n\n\n\n<li>Cek log pod cert-manager untuk melihat error lebih detail: <strong><em>kubectl logs -n cert-manager deploy\/cert-manager<\/em><\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Terkena_Rate_Limit_Lets_Encrypt\"><\/span>3. Terkena Rate Limit Let&#8217;s Encrypt<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s Encrypt production memiliki rate limit yang ketat, jadi gunakan mode staging untuk pengujian awal agar tidak menabrak batas tersebut. Beralih ke production hanya setelah semua konfigurasi terbukti berjalan benar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kalau sudah terlanjur kena rate limit, kamu harus menunggu sekitar satu minggu sebelum bisa request ulang ke endpoint production. Manfaatkan waktu ini untuk memastikan semua konfigurasi sudah bersih sebelum retry.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Secret_Name_Konflik_Antar_Domain\"><\/span>4. Secret Name Konflik Antar Domain<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Setiap domain wajib memiliki secretName yang berbeda di bagian tls pada manifest Ingress. Kalau dua domain menggunakan secret name yang sama, cert-manager akan bingung dan sertifikat bisa saling menimpa. Gunakan penamaan yang deskriptif dan konsisten, misalnya app1-tls, app2-tls, atau domain-nama-tls agar mudah diidentifikasi saat troubleshooting.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Ingress_Class_Tidak_Cocok\"><\/span>5. Ingress Class Tidak Cocok<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pastikan nilai ingress ClassName di manifest Ingress sesuai dengan Ingress controller yang terinstall di cluster kamu. Kalau kamu menggunakan NGINX, maka nilainya adalah nginx. Ketidakcocokan di sini akan membuat Ingress tidak diproses sama sekali oleh controller.<\/p>\n\n\n\n<div class=\"wp-block-button\" style=\"text-align: center;\"><a class=\"wp-block-button__link has-text-align-center wp-element-button\" href=\"https:\/\/rna.id\/\" target=\"_blank\" rel=\"noopener\">Reseller Domain Indonesia<\/a><\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Kesimpulan\"><\/span>Kesimpulan<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Setup multi domain di Kubernetes dengan NGINX Ingress dan Cert-Manager adalah cara yang efisien dan bebas biaya sertifikat jika menggunakan Let&#8217;s Encrypt. Kamu tidak perlu mengurus SSL secara manual, karena dari mulai penerbitan hingga pembaruan sertifikat semuanya akan berjalan otomatis. Tapi perlu diingat, tidak semua kebutuhan SSL bisa dipenuhi oleh Let&#8217;s Encrypt. Untuk aplikasi enterprise, <a href=\"https:\/\/rna.id\/blog\/contoh-website-toko-online\/\">website toko online<\/a>, atau sistem yang membutuhkan jaminan validasi lebih tinggi, butuh sertifikat SSL berbayar dengan fitur lebih lengkap. Kamu bisa <a href=\"https:\/\/rna.id\/\">beli sertifikat SSL di RNA<\/a> dengan berbagai pilihan yang sesuai kebutuhan <a href=\"https:\/\/rna.id\/blog\/ide-bisnis-online\/\">bisnis<\/a>.&nbsp; Mulai dari single domain, multi domain, hingga wildcard SSL, semua akan didukung oleh tim yang siap membantu proses konfigurasinya. Percayakan urusan SSL hanya di RNA!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Mengelola banyak domain dalam satu cluster Kubernetes bisa jadi mimpi buruk jika sertifikat SSL harus diurus satu per satu secara manual. Belum lagi risiko sertifikat expired yang bisa membuat website tidak aman. Kabar baiknya, ada cara untuk mengatasi kendala tersebut, yakni dengan menggabungkan NGINX Ingress Controller dan Cert-Manager.&nbsp; Metode ini bekerja dengan cara mengotomasi penerbitan [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4839,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rating_form_position":"","rating_results_position":"","mr_structured_data_type":"","footnotes":""},"categories":[19],"tags":[],"class_list":["post-4748","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domain"],"multi-rating":{"mr_rating_results":[{"adjusted_star_result":0,"star_result":0,"total_max_option_value":5,"adjusted_score_result":0,"score_result":0,"percentage_result":0,"adjusted_percentage_result":0,"count":0,"post_id":4748}]},"_links":{"self":[{"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/posts\/4748","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/comments?post=4748"}],"version-history":[{"count":3,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/posts\/4748\/revisions"}],"predecessor-version":[{"id":4751,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/posts\/4748\/revisions\/4751"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/media\/4839"}],"wp:attachment":[{"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/media?parent=4748"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/categories?post=4748"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rna.id\/blog\/wp-json\/wp\/v2\/tags?post=4748"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}