I am using the Jenkins K8s plugin (version 1.21) with the cloudbees-jenkins-distribution image (22.214.171.124-rolling)
I define my podTemplate in a k8s pod yaml, and then reference my pod yaml inside my Jenkinsfile like so:
Note that I reference a label and a yamlFile so that my build will pick up the pod if it already exists. I am seeing some weird behavior where if I make a change to the 'k8s-pod.yaml' inside my repo, that change is not reflected inside the pod that k8s wants to spin up (it takes the outdated pod yaml).
I can remove the label, then the new pod comes up fine (with it's own build_name_build_number pod name), but I am curious why it isn't picking up on the latest changes.
The Jenkins build logs point to the pod yaml at the correct commit.