完整的从CI到CD工具链使用argo，按照顺序
涉及两个repository（项目代码+yamls）和 一个镜像仓库
创建一个github token
https://github.com/settings/tokens
也可以使用配置文件，不过注意 token值是 base64编码之后的
apiVersion: v1
data:
token: xxxxxxxxxxxxxxxxxxxxxx
kind: Secret
metadata:
annotations:
lifecycle.cattle.io/create.secretsController_local: "true"
secret.user.cattle.io/secret: "true"
name: github-access
namespace: default
type: Opaque创建Event source
# Info on GitHub Webhook: https://developer.github.com/v3/repos/hooks/#create-a-hook
apiVersion: argoproj.io/v1alpha1
kind: EventSource
metadata:
name: github
namespace: argo
spec:
service:
ports:
- port: 12000
targetPort: 12000
github:
example:
repositories:
- owner: zl86790
names:
- argogithubsource
# Github will send events to following port and endpoint
webhook:
# endpoint to listen to events on
endpoint: /push
# port to run internal HTTP server on
port: "30001"
# HTTP request method to allow. In this case, only POST requests are accepted
method: POST
# url the event-source will use to register at Github.
# This url must be reachable from outside the cluster.
# The name for the service is in `<event-source-name>-eventsource-svc` format.
# You will need to create an Ingress or Openshift Route for the event-source service so that it can be reached from GitHub.
url: http://YOURIPADDRESS
# type of events to listen to.
# following listens to everything, hence *
# You can find more info on https://developer.github.com/v3/activity/events/types/
events:
- "*"
# apiToken refers to K8s secret that stores the github api token
# if apiToken is provided controller will create webhook on GitHub repo
# +optional
apiToken:
# Name of the K8s secret that contains the access token
name: github-access
# Key within the K8s secret whose corresponding value (must be base64 encoded) is access token
key: token
# # webhookSecret refers to K8s secret that stores the github hook secret
# # +optional
# webhookSecret:
# # Name of the K8s secret that contains the hook secret
# name: github-access
# # Key within the K8s secret whose corresponding value (must be base64 encoded) is hook secret
# key: secret
# type of the connection between event-source and Github.
# You should set it to false to avoid man-in-the-middle and other attacks.
insecure: true
# Determines if notifications are sent when the webhook is triggered
active: true
# The media type used to serialize the payloads
contentType: json
example-without-api-credentials:
owner: "argoproj"
repository: "argo"
webhook:
endpoint: "/push"
port: "13000"
method: "POST"
events:
- "*"
webhookSecret:
name: github-access
key: secret
insecure: true
active: true
contentType: "json"
# example-with-secure-connection:
# owner: "argoproj"
# repository: "argo"
# webhook:
# endpoint: "/push"
# port: "13000"
# method: "POST"
# url: "http://myargofakeurl.fake"
# # k8s secret that contains the cert
# serverCertSecret:
# name: my-secret
# key: cert-key
# # k8s secret that contains the private key
# serverKeySecret:
# name: my-secret
# key: pk-key
# events:
# - "push"
# - "delete"
# apiToken:
# name: github-access
# key: token
# webhookSecret:
# name: github-access
# key: secret
# insecure: true
# active: true
# contentType: "json"
apiVersion: v1
kind: ServiceAccount
metadata:
namespace: argo
name: operate-workflow-sa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: operate-workflow-role
namespace: argo
rules:
- apiGroups:
- argoproj.io
verbs:
- "*"
resources:
- workflows
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: operate-workflow-role-binding
namespace: argo
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: operate-workflow-role
subjects:
- kind: ServiceAccount
name: operate-workflow-sa
namespace: argosensor
# Info on GitHub Webhook: https://developer.github.com/v3/repos/hooks/#create-a-hook
apiVersion: argoproj.io/v1alpha1
kind: EventSource
metadata:
name: github
namespace: argo
spec:
service:
ports:
- port: 12000
targetPort: 12000
github:
example:
repositories:
- owner: zl86790
names:
- argogithubsource
# Github will send events to following port and endpoint
webhook:
# endpoint to listen to events on
endpoint: /push
# port to run internal HTTP server on
port: "12000"
# HTTP request method to allow. In this case, only POST requests are accepted
method: POST
# url the event-source will use to register at Github.
# This url must be reachable from outside the cluster.
# The name for the service is in `<event-source-name>-eventsource-svc` format.
# You will need to create an Ingress or Openshift Route for the event-source service so that it can be reached from GitHub.
url: http://13.115.24.93:30001
# type of events to listen to.
# following listens to everything, hence *
# You can find more info on https://developer.github.com/v3/activity/events/types/
events:
- "*"
# apiToken refers to K8s secret that stores the github api token
# if apiToken is provided controller will create webhook on GitHub repo
# +optional
apiToken:
# Name of the K8s secret that contains the access token
name: github-access
# Key within the K8s secret whose corresponding value (must be base64 encoded) is access token
key: token
# # webhookSecret refers to K8s secret that stores the github hook secret
# # +optional
# webhookSecret:
# # Name of the K8s secret that contains the hook secret
# name: github-access
# # Key within the K8s secret whose corresponding value (must be base64 encoded) is hook secret
# key: secret
# type of the connection between event-source and Github.
# You should set it to false to avoid man-in-the-middle and other attacks.
insecure: true
# Determines if notifications are sent when the webhook is triggered
active: true
# The media type used to serialize the payloads
contentType: json
example-without-api-credentials:
owner: "argoproj"
repository: "argo"
webhook:
endpoint: "/push"
port: "13000"
method: "POST"
events:
- "*"
webhookSecret:
name: github-access
key: secret
insecure: true
active: true
contentType: "json"
# example-with-secure-connection:
# owner: "argoproj"
# repository: "argo"
# webhook:
# endpoint: "/push"
# port: "13000"
# method: "POST"
# url: "http://myargofakeurl.fake"
# # k8s secret that contains the cert
# serverCertSecret:
# name: my-secret
# key: cert-key
# # k8s secret that contains the private key
# serverKeySecret:
# name: my-secret
# key: pk-key
# events:
# - "push"
# - "delete"
# apiToken:
# name: github-access
# key: token
# webhookSecret:
# name: github-access
# key: secret
# insecure: true
# active: true
# contentType: "json"sensor 创建完成之后，如果你提供了 github token，那么会自动创建 webhook
为了使用nodeport来开放 对应的 source pod，需要额外的 nodeport，默认它会创建一个 clusterip service
github-eventsource-svc
我们仿造它写一个nodeport
DEBUG 说明，这里如果出现了无法顺利触发 workflow的情况，请进行如下检查
2. Postman能否正确请求你的webhook，可以分别通过 映射端口 和 nodeport 测试
如果一切顺利
稍等片刻执行完成
目前没有找到直接trigger 既存的 workflow template 的方法，不过按照以下模式，把 template整个写进 sensor 配置文件的 trigger.template 还是可以运行的
缺点就是文件太长
apiVersion: argoproj.io/v1alpha1
kind: Sensor
metadata:
name: webhook
spec:
template:
serviceAccountName: operate-workflow-sa
dependencies:
- name: test-dep
eventSourceName: webhook
eventName: example
triggers:
- template:
name: argo-workflow-trigger
argoWorkflow:
group: argoproj.io
version: v1alpha1
resource: workflows
operation: submit
source:
resource:
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
generateName: buildkit-
namespace: argo
spec:
templates:
- name: main
dag:
tasks:
- name: clone
template: clone
arguments:
parameters:
- name: repo
value: '{{workflow.parameters.repo}}'
- name: branch
value: '{{workflow.parameters.branch}}'
- name: getcommitid
template: getcommitid
arguments: {}
depends: clone
- name: mountcommitid
template: mountcommitid
arguments: {}
depends: getcommitid
- name: build
template: build
arguments: {}
depends: mountcommitid
- name: image
template: image
arguments:
parameters:
- name: image
value: '{{workflow.parameters.image}}'
- name: commitid
value: '{{tasks.mountcommitid.outputs.parameters.commitid}}'
depends: build
- name: clone
inputs:
parameters:
- name: repo
- name: branch
container:
name: ''
image: 'alpine/git:v2.26.2'
args:
- clone
- '--depth'
- '1'
- '--branch'
- '{{inputs.parameters.branch}}'
- '--single-branch'
- '{{inputs.parameters.repo}}'
- .
workingDir: /work
volumeMounts:
- name: work
mountPath: /work
- name: getcommitid
inputs: {}
outputs: {}
metadata: {}
container:
name: ''
image: libaibai/getcommitid
command:
- /bin/bash
args:
- '-c'
- /getcommitid.sh
workingDir: /work
volumeMounts:
- name: work
mountPath: /work
- name: mountcommitid
outputs:
parameters:
- name: commitid
valueFrom:
path: /work/commitid.txt
default: mockup_commitid
metadata: {}
container:
name: ''
image: busybox
command:
- /bin/sh
args:
- '-c'
- ls /work
workingDir: /work
resources: {}
volumeMounts:
- name: work
mountPath: /work
- name: build
container:
name: ''
image: 'golang:alpine3.13'
command:
- go
args:
- build
- main.go
workingDir: /work
env:
- name: ENVTEST
value: helloworld
volumeMounts:
- name: work
mountPath: /work
- name: image
inputs:
parameters:
- name: image
- name: commitid
container:
name: ''
image: >-
gcr.io/kaniko-project/executor@sha256:f652f28537fa76e8f4f9393de13a064f0206003c451ce2ad6e4359fd5a21acbc
command:
- /kaniko/executor
args:
- '-f'
- /work/Dockerfile
- '-c'
- /work/
- >-
--destination={{inputs.parameters.image}}:{{inputs.parameters.commitid}}
workingDir: /work
env:
- name: envkey
value: envvalue
resources: {}
volumeMounts:
- name: work
mountPath: /work
- name: jenkins-docker-cfg
mountPath: /root
volumes:
- name: jenkins-docker-cfg
projected:
sources:
- secret:
name: regcred
items:
- key: .dockerconfigjson
path: .docker/config.json
entrypoint: main
arguments:
parameters:
- name: repo
value: 'https://USERNAME:YOURPASSWORD@github.com/zl86790/golanghelloworld.git'
- name: branch
value: master
- name: image
value: libaibai/argogolanghelloworld
volumeClaimTemplates:
- metadata:
name: work
creationTimestamp: null
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: local-path
status: {}
ttlStrategy:
secondsAfterCompletion: 1800
secondsAfterSuccess: 1800
secondsAfterFailure: 1800
使用 webhook trigger build
之前我们曾经创建过一个名叫 buildkit-vw57w 的 workflow template，这里如果想使用其他的template，也可以在sensor中配置
参考
https://github.com/argoproj/argo-events/tree/master/examples/sensors
https://github.com/argoproj/argo-events/discussions/1032
Event sensor 可以通过 trigger 对系统中既存的 workflow 进行 resubmit
例如，目前我们系统中存在一个 workflow template
然后我使用这个 workflow template来触发一个 workflow
然后我们使用 sensor 的trigger 来 resubmit 这个 workflow buildkit-vw57w-dwd7j
apiVersion: argoproj.io/v1alpha1
kind: Sensor
metadata:
name: webhook
spec:
template:
serviceAccountName: operate-workflow-sa
dependencies:
- name: test-dep
eventSourceName: webhook
eventName: example
triggers:
- template:
name: argo-workflow-trigger
argoWorkflow:
group: argoproj.io
version: v1alpha1
resource: workflows
operation: resubmit
source:
resource:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
name: buildkit-vw57w-dwd7j
namespace: argo
回顾一下之前的内容
sensor-controller 运行在 argo events 命名空间中，它需要通过trigger创建一个workflows/argoproj.io/v1alpha1资源。workspace的资源规范没有指定在哪个命名空间中创建资源，之前我们将 workflow 安装在了 argo 命名空间中。
sensor需要具有在argo命名空间中创建工作流/argoproj.io/v1alpha1资源权限的服务帐户。
创建需要的SA
apiVersion: v1
kind: ServiceAccount
metadata:
namespace: argo
name: operate-workflow-sa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: operate-workflow-role
namespace: argo
rules:
- apiGroups:
- argoproj.io
verbs:
- "*"
resources:
- workflows
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: operate-workflow-role-binding
namespace: argo
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: operate-workflow-role
subjects:
- kind: ServiceAccount
name: operate-workflow-sa
namespace: argo
sensor.yaml
apiVersion: argoproj.io/v1alpha1
kind: Sensor
metadata:
name: webhook
spec:
template:
serviceAccountName: operate-workflow-sa
dependencies:
- name: test-dep
eventSourceName: webhook
eventName: example
triggers:
- template:
name: webhook-workflow-trigger
k8s:
group: argoproj.io
version: v1alpha1
resource: workflows
operation: create
source:
resource:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: webhook-
spec:
entrypoint: whalesay
arguments:
parameters:
- name: message
# the value will get overridden by event payload from test-dep
value: hello world
templates:
- name: whalesay
inputs:
parameters:
- name: message
container:
image: docker/whalesay:latest
command: [cowsay]
args: ["{{inputs.parameters.message}}"]
parameters:
- src:
dependencyName: test-dep
dest: spec.arguments.parameters.0.valuekubectl -n argo apply -f sensor.yaml
通过webhook来触发这个workflow
kubectl -n argo port-forward $(kubectl -n argo get pod -l eventsource-name=webhook -o name) 12000:12000
curl -d '{"message":"hello argo"}' -H "Content-Type: application/json" -X POST http://localhost:12000/deploy
首先 argo event source 是需要额外安装的，和argoworkflow并不一起安装
参考 https://argoproj.github.io/argo-events/installation/
在没有安装的情况下会得到
Not Found: the server could not find the requested resource (get eventsources.argoproj.io)
官方文档中提供了两种安装方式
这里为了跟 workflow 的 UI 集成，所以我选择使用 Cluster-wide Installation 安装到argo namespace下
这里是官网的写法
Namespace Installation
kubectl create namespace argo-events
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/namespace-install.yaml
kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml
Cluster-wide Installation
kubectl create namespace argo-events
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install-validating-webhook.yaml
kubectl apply -n argo-events -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml
这里是我本地的写法
Cluster-wide Installation
kubectl create namespace argo-events
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install-validating-webhook.yaml
kubectl apply -n argo -f https://raw.githubusercontent.com/argoproj/argo-events/stable/examples/eventbus/native.yaml
可以看到 eventbus 的 命名空间是不一样的
Argo 的事件源 EventSource 可以是 webhook、s3、github、sqs 等 中间会经过 Eventbus （类似kafka的高性能分布式消息中间件），Eventbus 通过 sensor 来触发 trigger
具体有多少种 event sources 呢？
参考 https://github.com/argoproj/argo-events/tree/stable/examples/event-sources
这里将尝试 万能接口 webhook
apiVersion: argoproj.io/v1alpha1
kind: EventSource
metadata:
name: webhook
namespace: argo
spec:
service:
ports:
- port: 12000
targetPort: 12000
webhook:
example:
endpoint: /deploy
method: POST
port: "12000"
url: ""
进行一下测试
kubectl -n argo get pod -l eventsource-name=webhook -o name
kubectl -n argo port-forward $(kubectl -n argo get pod -l eventsource-name=webhook -o name) 12000:12000
curl -d '{"message":"hello argo"}' -H "Content-Type: application/json" -X POST http://localhost:12000/deploy
Argo 的事件源 EventSource 可以是 webhook、s3、github、sqs 等 中间会经过 Eventbus （类似kafka的高性能分布式消息中间件），Eventbus 通过 sensor 来触发 trigger
基于上一个例子，本例中将使用 commitid 来作为 image的tag
其中涉及了
因为 command 和 entrypoint 都无法使用 管道和重定向 （ args 都以参数形式提供 ）
所以这里使用了一个 ubuntu + shell 脚本的方式来 将 commitid 写入缓存文件
/getcommitid.sh
touch /work/$1/commitid.txt
git -C /work/$1 rev-parse HEAD > /work/$1/commitid.txt
ls /work
ls /work/$1
cat /work/$1/commitid.txtDockerfile
FROM ubuntu
RUN apt -y update && apt install -y git
COPY getcommitid.sh /
RUN chmod 777 /getcommitid.sh然后yaml文件内容
这里通过 output parameter 进行传递参数，请注意加粗的部分
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: buildkit-
namespace: argo
spec:
ttlStrategy:
secondsAfterCompletion: 1800 # Time to live after workflow is completed, replaces ttlSecondsAfterFinished
secondsAfterSuccess: 1800 # Time to live after workflow is successful
secondsAfterFailure: 1800 # Time to live after workflow fails
arguments:
parameters:
- name: repo
value: https://USERNAME:PASSWORD@github.com/zl86790/argo_build_demo_react.git
- name: branch
value: master
- name: path
value: helloworld
- name: image
value: libaibai/argobuilddemo
entrypoint: main
volumeClaimTemplates:
- metadata:
name: work
spec:
accessModes: [ "ReadWriteOnce" ]
# storageClassName: local-storage
storageClassName: local-path
resources:
requests:
storage: 1Gi
templates:
- name: main
dag:
tasks:
- name: clone
template: clone
arguments:
parameters:
- name: repo
value: "{{workflow.parameters.repo}}"
- name: branch
value: "{{workflow.parameters.branch}}"
- name: getcommitid
template: getcommitid
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "clone"
- name: mountcommitid
template: mountcommitid
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "getcommitid"
- name: install
template: install
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "mountcommitid"
- name: build
template: build
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "install"
- name: image
template: image
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
- name: image
value: "{{workflow.parameters.image}}"
- name: commitid
value: "{{tasks.mountcommitid.outputs.parameters.commitid}}"
depends: "build"
- name: clone
inputs:
parameters:
- name: repo
- name: branch
container:
volumeMounts:
- mountPath: /work
name: work
image: alpine/git:v2.26.2
workingDir: /work
# Do a shallow clone, which is the fastest way to clone, by using the
# --depth, --branch, and --single-branch options
args:
- clone
- --depth
- "1"
- --branch
- "{{inputs.parameters.branch}}"
- --single-branch
- "{{inputs.parameters.repo}}"
- .
- name: getcommitid
inputs:
parameters:
- name: path
container:
volumeMounts:
- mountPath: /work
name: work
image: libaibai/getcommitid
workingDir: /work
command:
- /bin/bash
args:
- -c
- "/getcommitid.sh {{inputs.parameters.path}}"
- name: mountcommitid
inputs:
parameters:
- name: path
outputs:
parameters:
- name: commitid
valueFrom:
default: "mockup_commitid" # Default value to use if retrieving valueFrom fails. If not provided workflow will fail instead
path: /work/{{inputs.parameters.path}}/commitid.txt
container:
volumeMounts:
- mountPath: /work
name: work
image: busybox
workingDir: /work/{{inputs.parameters.path}}
command:
- /bin/sh
args:
- -c
- "ls /work"
- name: install
inputs:
parameters:
- name: path
container:
image: node:14.17.3-alpine3.14
volumeMounts:
- mountPath: /work
name: work
workingDir: /work/{{inputs.parameters.path}}
env:
# Because this is not a Gomodule, we must turn modules off.
- name: ENVTEST
value: "helloworld"
command:
- npm
args:
- install
- name: build
inputs:
parameters:
- name: path
container:
image: node:14.17.3-alpine3.14
volumeMounts:
- mountPath: /work
name: work
workingDir: /work/{{inputs.parameters.path}}
env:
# Because this is not a Gomodule, we must turn modules off.
- name: ENVTEST
value: "helloworld"
command:
- npm
args:
- run
- build
- name: image
inputs:
parameters:
- name: path
- name: image
- name: commitid
# Mount the configuration so we can push the image.
# This should create the /.docker/config.json file.
volumes:
- name: jenkins-docker-cfg
projected:
sources:
- secret:
name: regcred
items:
- key: .dockerconfigjson
path: .docker/config.json
container:
# image: debug-v0.19.0
image: gcr.io/kaniko-project/executor@sha256:f652f28537fa76e8f4f9393de13a064f0206003c451ce2ad6e4359fd5a21acbc
volumeMounts:
- name: work
mountPath: /work
- name: jenkins-docker-cfg
mountPath: /root
workingDir: /work/{{inputs.parameters.path}}
env:
- name: envkey
value: envvalue
command:
- /kaniko/executor
args:
- -f
- /work/{{inputs.parameters.path}}/Dockerfile
- -c
- /work/{{inputs.parameters.path}}/
- --destination={{inputs.parameters.image}}:{{inputs.parameters.commitid}}
手动方式
kind: PersistentVolume
apiVersion: v1
metadata:
name: hp-pv-001
labels:
type: local
spec:
storageClassName: manual
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/tmp/data01"
kind: PersistentVolume
apiVersion: v1
metadata:
name: hp-pv-002
labels:
type: local
spec:
storageClassName: manual
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/tmp/data02"volumeClaimTemplates:
- metadata:
name: my-hostpath-volume
spec:
storageClassName: manual
accessModes: ["ReadWriteOnce"]
resources:
requests:
storage: 5Gi
selector:
matchLabels:
type: local或者使用
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: local-storage
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer第三种选择
kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/deploy/local-path-storage.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pvc/pvc.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pod/pod.yaml
本例将演示如何使用 Argo workflows 来进行一次完整的 CI/CD
在这个仓库中我们准备了一个简单的 react helloworld 项目
2. 创建 docker 权限用的 secrets
kubectl create secret docker-registry regcred --docker-server=https://index.docker.io/v1/ --docker-username=YOURNAME --docker-password=YOURPASSWORD --docker-email=YOUREMAIL@ADDRESS -n argo3. 准备dockerhub仓库
libaibai/argobuilddemo4. 创建 build.yaml 文件
参考 https://github.com/argoproj/argo-workflows/blob/master/examples/buildkit-template.yaml
为了方便测试，这里加入了 ttl 并且把官方文档上的 WorkflowTemplate 替换成了 Workflow
官方文档上使用的是 buildkit ，下面的例子中我使用的是 kaniko
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: buildkit-
namespace: argo
spec:
ttlStrategy:
secondsAfterCompletion: 1800 # Time to live after workflow is completed, replaces ttlSecondsAfterFinished
secondsAfterSuccess: 1800 # Time to live after workflow is successful
secondsAfterFailure: 1800 # Time to live after workflow fails
arguments:
parameters:
- name: repo
value: https://username:password@github.com/zl86790/argo_build_demo_react.git
- name: branch
value: master
- name: path
value: helloworld
- name: image
value: libaibai/argobuilddemo:latest
entrypoint: main
volumeClaimTemplates:
- metadata:
name: work
spec:
accessModes: [ "ReadWriteOnce" ]
# storageClassName: local-storage
storageClassName: local-path
resources:
requests:
storage: 1Gi
templates:
- name: main
dag:
tasks:
- name: clone
template: clone
arguments:
parameters:
- name: repo
value: "{{workflow.parameters.repo}}"
- name: branch
value: "{{workflow.parameters.branch}}"
- name: install
template: install
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "clone"
- name: build
template: build
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
depends: "install"
- name: image
template: image
arguments:
parameters:
- name: path
value: "{{workflow.parameters.path}}"
- name: image
value: "{{workflow.parameters.image}}"
depends: "build"
- name: clone
inputs:
parameters:
- name: repo
- name: branch
container:
volumeMounts:
- mountPath: /work
name: work
image: alpine/git:v2.26.2
workingDir: /work
# Do a shallow clone, which is the fastest way to clone, by using the
# --depth, --branch, and --single-branch options
args:
- clone
- --depth
- "1"
- --branch
- "{{inputs.parameters.branch}}"
- --single-branch
- "{{inputs.parameters.repo}}"
- .
- name: install
inputs:
parameters:
- name: path
container:
image: node:14.17.3-alpine3.14
volumeMounts:
- mountPath: /work
name: work
workingDir: /work/{{inputs.parameters.path}}
env:
# Because this is not a Gomodule, we must turn modules off.
- name: ENVTEST
value: "helloworld"
command:
- npm
args:
- install
- name: build
inputs:
parameters:
- name: path
container:
image: node:14.17.3-alpine3.14
volumeMounts:
- mountPath: /work
name: work
workingDir: /work/{{inputs.parameters.path}}
env:
# Because this is not a Gomodule, we must turn modules off.
- name: ENVTEST
value: "helloworld"
command:
- npm
args:
- run
- build
- name: image
inputs:
parameters:
- name: path
- name: image
# Mount the configuration so we can push the image.
# This should create the /.docker/config.json file.
volumes:
- name: jenkins-docker-cfg
projected:
sources:
- secret:
name: regcred
items:
- key: .dockerconfigjson
path: .docker/config.json
container:
# image: debug-v0.19.0
image: gcr.io/kaniko-project/executor@sha256:f652f28537fa76e8f4f9393de13a064f0206003c451ce2ad6e4359fd5a21acbc
volumeMounts:
- name: work
mountPath: /work
- name: jenkins-docker-cfg
mountPath: /root
workingDir: /work/{{inputs.parameters.path}}
env:
- name: envkey
value: envvalue
command:
- /kaniko/executor
args:
- -f
- /work/{{inputs.parameters.path}}/Dockerfile
- -c
- /work/{{inputs.parameters.path}}/
- --destination={{inputs.parameters.image}}
此例子中使用的
storageClassName: local-path
是通过以下脚本创建的，但是只能使用在 测试环境中 参考 使用hostpath作为VolumeClaimsTemplate
当然如果真的没有办法使用NFS卷或者其他可共享的pv卷，可以考虑使用 nodeselector 将build pod固定在某个特殊的节点上
kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/deploy/local-path-storage.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pvc/pvc.yaml使用的Dockerfile
FROM nginx:1.19
COPY build /usr/share/nginx/html