From 060248f6e30f76482fe5fb3211da3d6b76efe762 Mon Sep 17 00:00:00 2001 From: Ben Vincent Date: Sat, 21 Mar 2026 23:53:51 +1100 Subject: [PATCH] fix: connect puppetboard to puppetdb over SSL on port 8081 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Puppetboard was connecting to PuppetDB on port 8080 (plain HTTP), causing 403 Forbidden errors on the /metrics/v2 Jolokia endpoint which requires HTTPS with a Puppet certificate. Also replaced the invalid PUPPETDB_SSL_SKIP_VERIFY var with the correct PUPPETDB_SSL_VERIFY, PUPPETDB_CERT, and PUPPETDB_KEY pointing to the certs already generated by the cert-generator init container. 💘 Generated with Crush Assisted-by: Claude Sonnet 4.6 via Crush --- apps/base/puppet/configmap_puppetboard-config.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/apps/base/puppet/configmap_puppetboard-config.yaml b/apps/base/puppet/configmap_puppetboard-config.yaml index a546c70..3a5ce6e 100644 --- a/apps/base/puppet/configmap_puppetboard-config.yaml +++ b/apps/base/puppet/configmap_puppetboard-config.yaml @@ -11,8 +11,10 @@ metadata: namespace: puppet data: PUPPETDB_HOST: "puppetdb" - PUPPETDB_PORT: "8080" - PUPPETDB_SSL_SKIP_VERIFY: "True" + PUPPETDB_PORT: "8081" + PUPPETDB_SSL_VERIFY: "/opt/puppetboard/ssl/ca.pem" + PUPPETDB_CERT: "/opt/puppetboard/ssl/puppetboard.pem" + PUPPETDB_KEY: "/opt/puppetboard/ssl/puppetboard.key" LOGLEVEL: "debug" PUPPETDB_TIMEOUT: "20" UNRESPONSIVE_HOURS: "3"