-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.345
Kubernetes plugin Version 3580.v78271e5631dc
i can't get this to work for secrets or configmaps... i've this config in my helmrelease, and it works if i just leave the persistentVolumeClaim resource in there... once i add any of the configmap (which is just a test) or even 1 of the 2 secrets needed to access a nexus3 repo (and each of them exist in same jenkins namespace, cm and secrets), the resulting pod will include just the jnlp container and never the maven one...
maven-0-7-0-nexus2: |
- name: maven
label: jenkins-maven-0-7-0-nexus2
serviceAccount: jenkins
containers:
- name: maven
image: ghcr.io/ecomind/jenkins-agent-maven:0.7.0
command: "cat"
ttyEnabled: true
privileged: true
resourceRequestCpu: "1"
resourceRequestMemory: "2Gi"
resourceLimitCpu: "2"
resourceLimitMemory: "4Gi"
volumes:
- persistentVolumeClaim:
mountPath: /home/jenkins/.m2/repository
claimName: maven
readOnly: false
- configMapVolume:
configMapName: cm-test
mountPath: /tmp/ui.properties
subPath: ui.properties
- secretVolume:
mountPath: /home/jenkins/.m2
secretName: nexus-settings
- secretVolume:
mountPath: /home/jenkins/.m2
secretName: nexus-settings-security
can't find an example of this, but what i did is coherent with official docs...