Compare commits
1 Commits
doc/helm-r
...
feat/helm-
Author | SHA1 | Date | |
---|---|---|---|
95d4a1e13e |
@ -1,6 +0,0 @@
|
|||||||
To be able to run helm inside a jenkins pod, you'll need to
|
|
||||||
* create a role in the namespace where tiller is installed
|
|
||||||
* bind that role to the user that jenkins pods run as
|
|
||||||
|
|
||||||
This directory contains yaml for these resources.
|
|
||||||
See also https://github.com/helm/helm/blob/master/docs/rbac.md
|
|
@ -1,13 +0,0 @@
|
|||||||
apiVersion: rbac.authorization.k8s.io/v1beta1
|
|
||||||
kind: RoleBinding
|
|
||||||
metadata:
|
|
||||||
name: tiller-jenkins-binding
|
|
||||||
namespace: kube-system
|
|
||||||
roleRef:
|
|
||||||
apiGroup: rbac.authorization.k8s.io
|
|
||||||
kind: Role
|
|
||||||
name: tiller-user
|
|
||||||
subjects:
|
|
||||||
- kind: ServiceAccount
|
|
||||||
name: default
|
|
||||||
namespace: molgenis-jenkins
|
|
@ -1,18 +0,0 @@
|
|||||||
apiVersion: rbac.authorization.k8s.io/v1beta1
|
|
||||||
kind: Role
|
|
||||||
metadata:
|
|
||||||
name: tiller-user
|
|
||||||
namespace: kube-system
|
|
||||||
rules:
|
|
||||||
- apiGroups:
|
|
||||||
- ""
|
|
||||||
resources:
|
|
||||||
- pods/portforward
|
|
||||||
verbs:
|
|
||||||
- create
|
|
||||||
- apiGroups:
|
|
||||||
- ""
|
|
||||||
resources:
|
|
||||||
- pods
|
|
||||||
verbs:
|
|
||||||
- list
|
|
@ -416,6 +416,12 @@ jenkins:
|
|||||||
key: VAULT_ADDR
|
key: VAULT_ADDR
|
||||||
secretName: molgenis-pipeline-vault-secret
|
secretName: molgenis-pipeline-vault-secret
|
||||||
secretKey: addr
|
secretKey: addr
|
||||||
|
helm:
|
||||||
|
Image: "lachlanevenson/k8s-helm"
|
||||||
|
ImageTag: "v2.10.0"
|
||||||
|
Command: cat
|
||||||
|
WorkingDir: /home/jenkins
|
||||||
|
TTY: true
|
||||||
NodeSelector: {}
|
NodeSelector: {}
|
||||||
node:
|
node:
|
||||||
Label: node-carbon
|
Label: node-carbon
|
||||||
|
Reference in New Issue
Block a user