[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-55887 Allow addition of custom resource limits in kubernetes containers Change By: Jesse Glick Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197286.1548929898000.12885.1563306207210%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title Steffen Seckler commented on JENKINS-55887 Re: Allow addition of custom resource limits in kubernetes containers ok, just saying that it would be nice for the more inexperienced users to have an easy option to add these limitations. Fyi: got the raw input working with: spec: serviceAccount: nvidia-deviceplugin serviceAccountName: nvidia-deviceplugin containers: - name: cuda-10 image: "nvidia/cuda:10.0-devel-centos7" env: - name: NVIDIA_VISIBLE_DEVICES value: all - name: NVIDIA_DRIVER_CAPABILITIES value: "compute,utility" - name: NVIDIA_REQUIRE_CUDA value: "cuda>=5.0" - name: HOME value: /home/jenkins tty: true args: - cat command: - /bin/bash - -i - -c securityContext: privileged: true resources: limits: nvidia.com/gpu: 1 # requesting 1 GPU especially the tty+command part should not be forgotten. Do I actually need to infuse the jenkins secrets somehow? or are they only relevant for the default (jnlp) container Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title
Steffen Seckler edited a comment on JENKINS-55887
Re: Allow addition of custom resource limits in kubernetes containers
ok, just saying that it would be nice for the more inexperienced users to have an easy option to add these limitations.Fyi: got the raw input working with:{code}spec: serviceAccount: nvidia-deviceplugin serviceAccountName: nvidia-deviceplugin containers:- name: cuda-10 image: "nvidia/cuda:10.0-devel-centos7" env:- name: NVIDIA_VISIBLE_DEVICES value: all- name: NVIDIA_DRIVER_CAPABILITIES value: "compute,utility"- name: NVIDIA_REQUIRE_CUDA value: "cuda>=5.0"- name: HOME value: /home/jenkins tty: true args:- cat command:- /bin/bash- -i- -c securityContext:privileged: true resources:limits: nvidia.com/gpu: 1 # requesting 1 GPU{code}especially the tty+command part should not be forgotten. Do I actually need to infuse the jenkins secrets somehow? or are they only relevant for the default (jnlp) container ?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title Carlos Sanchez commented on JENKINS-55887 Re: Allow addition of custom resource limits in kubernetes containers the yaml option is there so we don't need to write new ui/methods for each possible k8s api option Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title Steffen Seckler updated an issue Jenkins / JENKINS-55887 Allow addition of custom resource limits in kubernetes containers Change By: Steffen Seckler Issue Type: New Feature Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55887) Allow addition of custom resource limits in kubernetes containers
Title: Message Title Steffen Seckler created an issue Jenkins / JENKINS-55887 Allow addition of custom resource limits in kubernetes containers Issue Type: New Feature Assignee: Carlos Sanchez Attachments: image-2019-01-31-11-14-25-885.png Components: kubernetes-plugin Created: 2019-01-31 10:18 Labels: kubernetes-plugin Priority: Minor Reporter: Steffen Seckler Description Currently, it is not possible to add custom resource limits to kubernetes containers unless you write raw yaml. A rudimentary example would be: ... containers: - name: NAME ... resources: limits: nvidia.com/gpu: 1 # requesting 1 GPU ... Here the last line cannot be added easily with the interface. Possible Solution Add this functionality similar to the EnvVars variable, where multiple limits can be defined by hand with name and value. So basically replace EnvVars with limits in the following screenshot: Additional Context A complete example (not for jenkins) would be: apiVersion: v1 kind: Pod metadata: name: cuda-vector-add namespace: nvidia spec: restartPolicy:
