Lets encrypt server certificate verification failed

Hi, we’re using Jenkins pod with slave pods (as cloud w/kubernetes pluging) .
our Git repo is Atlassian BitBucket signed with Let’s encrypt SSL .
As of last week , due to change by Let’s encrypt , our Jenkins cannot access BB repos and throws error,
server certificate verification failed. CAfile: none CRLfile: none.
According to Lets Encrypt web site, one needs to update CA trust files in running OS.
Since we’re using Jenkins POD . we cannot update container OS . tried to upgrade jenkins pod to Latest version (using Helm) but It didnt help .
So now our R&D are stuck .
Urgent Help needed . Thanks

Which docker image are you using? I’m pretty sure the newer ones should be fine, but if your using a older one you’ll probably have to extend it, switch to root, update certs then switch back to Jenkins.

Docker image updates shows how to extend any image you want

Reminder, please use the term agent instead of slave. Slave has been removed for years now.

In the past, an outdated Java version seemed to be associated with SSL certificate recognition failures.

As @halkeye noted, if you’re running the current versions of the Docker images, you’ll have a current Java version and a current operating system version. If you’re not running the current versions of the Docker images, you’ll benefit from updating to the current versions.