-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdeployment.yaml
66 lines (66 loc) · 1.76 KB
/
deployment.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
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "1"
creationTimestamp: "2019-04-06T20:31:56Z"
generation: 1
labels:
run: hackunt-server
name: hackunt-server
namespace: default
resourceVersion: "5776"
selfLink: /apis/extensions/v1beta1/namespaces/default/deployments/hackunt-server
uid: 05a3cfa7-58ab-11e9-839f-42010a80007e
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 2
selector:
matchLabels:
run: hackunt-server
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
run: hackunt-server
spec:
containers:
- image: robotlaserbeam/hackunt-server
imagePullPolicy: Always
name: hackunt-server
ports:
- containerPort: 3000
protocol: TCP
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
status:
availableReplicas: 1
conditions:
- lastTransitionTime: "2019-04-06T20:31:56Z"
lastUpdateTime: "2019-04-06T20:31:59Z"
message: ReplicaSet "hackunt-server-7767d6fb69" has successfully progressed.
reason: NewReplicaSetAvailable
status: "True"
type: Progressing
- lastTransitionTime: "2019-04-06T20:40:47Z"
lastUpdateTime: "2019-04-06T20:40:47Z"
message: Deployment has minimum availability.
reason: MinimumReplicasAvailable
status: "True"
type: Available
observedGeneration: 1
readyReplicas: 1
replicas: 1
updatedReplicas: 1