informatic
2afe604595
cluster/kube: minor cert-manager cleanups, disable webhooks by default
2019-04-02 14:43:34 +02:00
informatic
79ddbc57d9
cluster/kube: initial cert-manager implementation
2019-04-02 13:20:15 +02:00
q3k
65f3b1d8ab
cluster/kube: add waw-hdd-redundant-1 pool/storageclass
2019-04-02 01:05:38 +02:00
q3k
c6da127d3f
cluster/kube: ceph-waw1 up
2019-04-02 00:06:13 +02:00
q3k
cdfafaf91e
cluster/kube: finish rook operator
2019-04-01 19:16:18 +02:00
q3k
b7fcc67f42
cluster/kube: start implementing rook
2019-04-01 18:40:50 +02:00
q3k
14cbacb81a
cluster/kube/metallb: parametrize address pools
2019-04-01 18:00:44 +02:00
q3k
a9c7e86687
cluster: fix metallb, add nginx ingress controller
2019-04-01 17:56:28 +02:00
q3k
1e565dc4a5
cluster: start implementing metallb
2019-01-18 09:40:59 +01:00
q3k
e3af1eb852
cluster: autodetect IP address
...
This is so that Calico starts with the proper subnet. Feeding it just an
IP from the node status will mean it parses it as /32 and uses IPIP
tunnels for all connectivity.
2019-01-18 09:39:57 +01:00
q3k
5c75574464
cluster/coredns: allow resolving via <svc>.<namespace>.svc.k0.hswaw.net
2019-01-17 21:35:10 +01:00
q3k
af3be426ad
cluster: deploy calico and metrics service
2019-01-17 18:57:19 +01:00
q3k
49b9a13d28
cluster: deploy coredns
2019-01-14 00:02:59 +01:00
q3k
5bebbebe3e
cluster/kube: fix typo
2019-01-13 22:08:05 +01:00
q3k
4d9e72cb8c
cluster/kube: init
2019-01-13 22:06:33 +01:00