[JIRA] (JENKINS-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez updated JENKINS-42851 Jenkins / JENKINS-42851 secretVolume not created read only Change By: Carlos Sanchez Status: Resolved Fixed but Unreleased 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez updated JENKINS-42851 Jenkins / JENKINS-42851 secretVolume not created read only Change By: Carlos Sanchez Status: Fixed but Unreleased Resolved Resolution: Not A Defect Fixed 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-42851) secretVolume not created read only
Title: Message Title Wes Couch commented on JENKINS-42851 Re: secretVolume not created read only This has been resolved in this PR https://github.com/jenkinsci/kubernetes-plugin/pull/452 . You can now set defaultMode in the pod template since version 1.15.0 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez commented on JENKINS-42851 Re: secretVolume not created read only something like the example k8s provides apiVersion: v1 kind: Pod metadata: name: mypod spec: containers: - name: maven image: maven:alpine volumeMounts: - name: foo mountPath: "/etc/foo" volumes: - name: foo secret: secretName: mysecret defaultMode: 256 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Bill Warner commented on JENKINS-42851 Re: secretVolume not created read only Carlos Sanchez is there an example on how to get the defaultmode injected into the correct array index of the secret volume? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez commented on JENKINS-42851 Re: secretVolume not created read only https://github.com/jenkinsci/kubernetes-plugin/#using-yaml-to-define-pod-templates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Vladislav Trayanov commented on JENKINS-42851 Re: secretVolume not created read only Sorry, for the dumb question, but how to use the yaml syntax of the plugin? Not sure where I can find it in the docs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez commented on JENKINS-42851 Re: secretVolume not created read only This works as expected, no permissions are passed to kubernetes see https://kubernetes.io/docs/concepts/configuration/secret You can also specify the permission mode bits files part of a secret will have. If you don’t specify any, 0644 is used by default. You can specify a default mode for the whole secret volume and override per key if needed. You can override the default by using the yaml syntax in the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez resolved as Not A Defect Jenkins / JENKINS-42851 secretVolume not created read only Change By: Carlos Sanchez Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title Vladislav Trayanov commented on JENKINS-42851 Re: secretVolume not created read only I had the same issue. I mount private key as a secret volume and actually, the permissions are 777 on pod side Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42851) secretVolume not created read only
Title: Message Title
J Knurek created an issue
Jenkins / JENKINS-42851
secretVolume not created read only
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Mar/16 4:47 PM
Priority:
Minor
Reporter:
J Knurek
use case:
pipeline
podTemplate(label: 'jenkpod', containers: [
containerTemplate(name: 'golang', image: 'golang:1.8', ttyEnabled: true, command: 'cat')
], volumes: [
secretVolume(secretName: 'jenkins-key-secret', mountPath: '/root/.ssh')
]) {
node ('jenkpod') { container('golang') {
stage('Pre-Build') {
sh 'ls -al /root/.ssh'
sh 'ssh -vT -i /root/.ssh/ssh-publickey -o "StrictHostKeyChecking=no" g...@github.com'
}
} }
}
snippet of generated yaml
- apiVersion: v1
kind: Pod
metadata:
spec:
containers:
- command:
- cat
env:
- name: JENKINS_LOCATION_URL
value: http://
- name: HOME
value: /home/jenkins
image: golang:1.8
name: golang
tty: true
volumeMounts:
- mountPath: /root/.ssh
name: volume-0
- mountPath: /home/jenkins
name:
