Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. 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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • kubernetes-plugin
    • 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
      ...

            Unassigned Unassigned
            hanxinhang han xinhang
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: