-
Bug
-
Resolution: Unresolved
-
Critical
-
None
When I use the persistent volume claim of kubernetes plugin and set read-only, readonly is now set under volumes, which should be under volumemounts. This will cause the actually mounted directory to still be written to or even deleted, which is dangerous
-----------------------------------
expect:
-----------------------------------
...
volumeMounts:
- mountPath: "/tools"
name: "volume-1"
readOnly: true
...
volumes:
- name: "volume-1"
persistentVolumeClaim:
claimName: "jenkins-tools-pvc"
...
-----------------------------------
actual (This is wrong):
-----------------------------------
...
volumeMounts:
- mountPath: "/tools"
name: "volume-1"
readOnly: false
...
volumes:
- name: "volume-1"
persistentVolumeClaim:
claimName: "jenkins-tools-pvc"
readOnly: true
...
I can only confirm the issue
Using version 3893.v73d36f3b_9103 of the plugin.
Is there currently a workaround?