This repository has been archived by the owner on Dec 12, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathservice.yaml
165 lines (165 loc) · 4.82 KB
/
service.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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
---
# Deployment of our jira-service
apiVersion: apps/v1
kind: Deployment
metadata:
name: jira-service
namespace: keptn
spec:
selector:
matchLabels:
run: jira-service
replicas: 1
template:
metadata:
labels:
run: jira-service
app.kubernetes.io/name: jira-service
app.kubernetes.io/version: 0.8.6
spec:
containers:
- name: jira-service
image: keptnsandbox/jira-service:0.8.6
ports:
- containerPort: 8080
env:
- name: CONFIGURATION_SERVICE
value: 'http://configuration-service:8080'
- name: JIRA_BASE_URL
valueFrom:
secretKeyRef:
name: jira-details
key: jira-base-url
- name: JIRA_USERNAME
valueFrom:
secretKeyRef:
name: jira-details
key: jira-username
- name: JIRA_REPORTER_ID
valueFrom:
secretKeyRef:
name: jira-details
key: jira-reporter-user-id
- name: JIRA_ASSIGNEE_ID
valueFrom:
secretKeyRef:
name: jira-details
key: jira-assignee-user-id
- name: JIRA_API_TOKEN
valueFrom:
secretKeyRef:
name: jira-details
key: jira-api-token
- name: JIRA_PROJECT_KEY
valueFrom:
secretKeyRef:
name: jira-details
key: jira-project-key
- name: JIRA_ISSUE_TYPE
valueFrom:
secretKeyRef:
name: jira-details
key: jira-issue-type
- name: JIRA_TICKET_FOR_PROBLEMS
valueFrom:
secretKeyRef:
name: jira-details
key: jira-create-ticket-for-problems
- name: JIRA_TICKET_FOR_EVALUATIONS
valueFrom:
secretKeyRef:
name: jira-details
key: jira-create-ticket-for-evaluations
- name: DT_TENANT
valueFrom:
secretKeyRef:
name: dynatrace
key: DT_TENANT
optional: true
- name: DT_API_TOKEN
valueFrom:
secretKeyRef:
name: dynatrace
key: DT_API_TOKEN
optional: true
- name: KEPTN_DOMAIN
valueFrom:
secretKeyRef:
name: jira-details
key: keptn-domain
- name: KEPTN_BRIDGE_URL
valueFrom:
secretKeyRef:
name: jira-details
key: keptn-bridge-url
optional: true
- name: SEND_EVENT
value: 'true'
- name: DEBUG
value: 'false'
- name: distributor
image: keptn/distributor:0.8.4
livenessProbe:
httpGet:
path: /health
port: 10999
initialDelaySeconds: 5
periodSeconds: 5
imagePullPolicy: Always
ports:
- containerPort: 8080
resources:
requests:
memory: "16Mi"
cpu: "25m"
limits:
memory: "128Mi"
cpu: "250m"
env:
- name: PUBSUB_URL
value: 'nats://keptn-nats-cluster'
- name: PUBSUB_TOPIC
value: 'sh.keptn.>'
- name: PUBSUB_RECIPIENT
value: '127.0.0.1'
- name: VERSION
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: 'metadata.labels[''app.kubernetes.io/version'']'
- name: K8S_DEPLOYMENT_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: 'metadata.labels[''app.kubernetes.io/name'']'
- name: K8S_POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
- name: K8S_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
- name: K8S_NODE_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: spec.nodeName
serviceAccountName: keptn-default
---
# Expose jira-service via Port 8080 within the cluster
apiVersion: v1
kind: Service
metadata:
name: jira-service
namespace: keptn
labels:
run: jira-service
spec:
ports:
- port: 8080
protocol: TCP
selector:
run: jira-service