-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathworkflow.yaml
84 lines (83 loc) · 2.08 KB
/
workflow.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
version: v1
description: Nebula Workflow
steps:
- name: Step 1 - Initialize Workflow
image: alpine:latest
input:
- echo "Initializing workflow"
- name: Step 2a - Deployments via kubectl
image: gcr.io/nebula-tasks/nebula-kubectl:57d9f2b
spec:
command: apply
file: deploy/deployments.yaml
namespace: heath-dev
cluster:
name: shared-k8s-dev-cluster
url:
$type: Secret
name: url
cadata:
$type: Secret
name: cadata
token:
$type: Secret
name: token
git:
name: nebula-workflow-examples
repository: https://github.com/heathseals/nebula-workflow-examples.git
dependsOn:
- Step 1 - Initialize Workflow
- name: Step 2b - Services via kubectl
image: gcr.io/nebula-tasks/nebula-kubectl:57d9f2b
spec:
command: apply
file: deploy/services.yaml
namespace: heath-dev
cluster:
name: shared-k8s-dev-cluster
url:
$type: Secret
name: url
cadata:
$type: Secret
name: cadata
token:
$type: Secret
name: token
git:
name: nebula-workflow-examples
repository: https://github.com/heathseals/nebula-workflow-examples.git
dependsOn:
- Step 2a - Deployments via kubectl
- name: Step 2c - Ingress via kubectl
image: gcr.io/nebula-tasks/nebula-kubectl:57d9f2b
spec:
command: apply
file: deploy/ingress.yaml
namespace: heath-dev
cluster:
name: shared-k8s-dev-cluster
url:
$type: Secret
name: url
cadata:
$type: Secret
name: cadata
token:
$type: Secret
name: token
git:
name: nebula-workflow-examples
repository: https://github.com/heathseals/nebula-workflow-examples.git
dependsOn:
- Step 2b - Services via kubectl
- name: Step 3 - Notify via Slack
image: gcr.io/nebula-tasks/nebula-slack-notification:57d9f2b
spec:
apitoken:
$type: Secret
name: slack-token
channel: "#team-infracore-nebula-workflows"
message: "Deployment succeeded!"
dependsOn:
- Step 2c - Ingress via kubectl