Plugin update behaviour with custom container images and Kubernetes persistent volumes

[halkeye (Gavin Mogan)]

@richardmilnerwatts

Adding a new plugin to the container image using jenkins-plugin-cli is copied to the EFS volume during deletion/recreation of the controller. This is UNEXPECTED and implies there is another process acting to copy file(s) from the container image to the EFS volume.

yes, on startup /usr/share/jenkins/ref/plugins is copied to jenkins home without rewriting anything

@richardmilnerwatts

Removing the plugin folder from the EFS volume before deleting/recreating the jenkins controller pod causes the plugin folder from the container image to be copied into the EFS volume, bringing across all installed/updated plugins. This is UNEXPECTED.

see previous

@richardmilnerwatts

I have a working upgrade process now, which is to build a new custom image with my desired plugins and then move the plugin folder elsewhere on the EFS volume before recreating the pod.

This is exactly what overwritePlugins value in the helm chart does, it rm $JENKINS_HOME/plugins/ on init so startup can copy plugins over from the image

jenkinsci/helm-charts/blob/90ac3df0febca1c9f4223ca6b142910272018654/charts/jenkins/values.yaml#L261-L262

Hope this is what your asking, you didn’t really ask a question.