The purpose of this document is to guide you through challenges you might face with setting up Jenkins on Kubernetes while behind a proxy. Some corporate proxies intercept httpS communications by changing the cert, this causes Jenkins and other tools to fail while trying to connect to target urls.
A proper way to fix issues with self-sign certificate (which is the case if your corporate proxy intercepts httpS communications) is to add the corporate' certs to Jenkins JVM as well as its OS. However, to begin with, we first start with a quick fix: Adding proxy configs and forcing Jenkins to get updates from http://updates.jenkins.io
(Notice it's not a httpS endpoint).
persistence:
enabled: true
storageClass: local-storage