• Type: Bug
• Resolution: Unresolved
• Priority: Critical
• Component/s: kubernetes-plugin
• Labels:

  None

[JENKINS-68978] 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

han xinhang created issue - 2022-07-11 03:29

han xinhang made changes - 2022-07-11 03:32

Description

Original: 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

New: 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

han xinhang made changes - 2022-07-11 03:32

Description

Original: 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

New: 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 ...

Collapse comment: Damien Coraboeuf added a comment - 2023-03-16 13:03, Edited by Damien Coraboeuf - 2023-03-16 13:04

Damien Coraboeuf added a comment - 2023-03-16 13:03 - edited

I can only confirm the issue Using version 3893.v73d36f3b_9103 of the plugin.

Is there currently a workaround?

Expand comment: Damien Coraboeuf added a comment - 2023-03-16 13:03, Edited by Damien Coraboeuf - 2023-03-16 13:04

Damien Coraboeuf added a comment - 2023-03-16 13:03 - edited I can only confirm the issue Using version 3893.v73d36f3b_9103 of the plugin. Is there currently a workaround?