[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

jenkins-ci@carlossanchez.eu (JIRA)

unread,

May 25, 2018, 4:52:02 AM5/25/18

to jenkinsc...@googlegroups.com

Carlos Sanchez commented on

JENKINS-47591

Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

I believe this should be possible to configure now with the yaml syntax

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

jenkins-ci@carlossanchez.eu (JIRA)

unread,

May 25, 2018, 4:56:02 AM5/25/18

to jenkinsc...@googlegroups.com

Carlos Sanchez resolved as Won't Do

Jenkins /

JENKINS-47591

Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

Change By:	Carlos Sanchez
Status:	Open Resolved
Resolution:	Won't Do

Add Comment

vic@pleexy.com (JIRA)

unread,

Feb 9, 2019, 8:10:03 PM2/9/19

to jenkinsc...@googlegroups.com

Vic K commented on

JENKINS-47591

Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

As far as I understand, it's possible to use PVC for home directory through yaml, however, PVC has to be referred by name, which means it'll be shared between all slave pods. It doesn't really solve the problem.

What would be great is an ability to provide PVC template that plugin would use to create a pvc for every slave pod.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jenkins-ci@carlossanchez.eu (JIRA)

unread,

Feb 10, 2019, 4:41:01 AM2/10/19

to jenkinsc...@googlegroups.com

Carlos Sanchez commented on

JENKINS-47591

Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

That's a different issue, and you can only use pwc templates with statefulsets

Add Comment

pablo.gomezjimenez@dhl.com (JIRA)

unread,

Sep 12, 2019, 10:28:01 AM9/12/19

to jenkinsc...@googlegroups.com

Pablo Gomez commented on

JENKINS-47591

Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

Hi, we are facing the same issue. We have performance problems accessing from slaves to our persistent storage when we have multiple slaves running in the same node. Is there any solution or alternative? Is there any way to configure a separate claim for each pod?