forked from Boostport/kubernetes-vault
-
Notifications
You must be signed in to change notification settings - Fork 0
/
kubernetes-vault.yaml
63 lines (61 loc) · 1.46 KB
/
kubernetes-vault.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
apiVersion: v1
kind: Service
metadata:
name: kubernetes-vault
labels:
run: kubernetes-vault
spec:
clusterIP: None
selector:
run: kubernetes-vault
# Kubernetes-Vault does not need to expose any ports through a headless service.
# However, there's a Kubernetes bug where the pods won't be registered in the API,
# so we need to use this hack. See kubernetes/kubernetes#32796
ports:
- name: port
port: 80
---
apiVersion: v1
kind: ConfigMap
metadata:
name: kubernetes-vault
data:
kubernetes-vault.yml: |-
vault:
addr: http://vault:8200
token: 91526d9b-4850-3405-02a8-aa29e74e17a5
kubernetes:
watchNamespace: ${KUBERNETES_NAMESPACE}
serviceNamespace: ${KUBERNETES_NAMESPACE}
service: kubernetes-vault
prometheus:
tls:
vaultCertBackend: intermediate-ca
vaultCertRole: kubernetes-vault
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: kubernetes-vault
spec:
replicas: 3
template:
metadata:
labels:
run: kubernetes-vault
spec:
containers:
- name: kubernetes-vault
image: boostport/kubernetes-vault:0.4.4
env:
- name: KUBERNETES_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
volumeMounts:
- name: config-volume
mountPath: /kubernetes-vault
volumes:
- name: config-volume
configMap:
name: kubernetes-vault