Using jenkins/inbound-agent image reports version 4.13 or newer is required

Using Jenkins
,
9

I genuinely appreciate your help. After exploring all the options, I carefully reviewed the pipeline and we had a step that overrode the image which I would specify in the Jenkinsfile. An older version of the pipeline was active which hardcoded agent configuration in the build step. Please see below. I wasn’t aware that this config will overwrite whatever is specified in the Pod Template configuration on the Jenkins Cloud configuration. After updating the image here, I am able to successfully run the pipeline.

stage('Deploy K8s Resources and replace placeholder values') {
      agent {
        kubernetes {
          cloud "${JENKINS_CLOUD_NAME}"
          yaml '''
            apiVersion: v1
            kind: Pod
            metadata:
              labels:
                some-label: some-label-value
            spec:
              serviceAccountName: jenkins-dev-serviceaccount
              automountServiceAccountToken: true
              containers:
              - name: jnlp
                image: <This_was_the_hardcoded_piece>:v4
                command:
                - /usr/local/bin/jenkins-agent
                tty: true