117 Commits (c410432d947f516d7c1de8e85791e134f041165a)

Author	SHA1	Message	Date
q3k	eeed6fb6da	recertify all certs	2019-04-01 16:19: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	41bd2b52c2	cluster/secrets: add implr	2019-01-17 23:37:36 +01:00
q3k	f3010ee1cb	cluster/secrets: add cz2	2019-01-17 21:35:52 +01:00
q3k	dc9c29ac90	cluster: add calico key	2019-01-17 21:35:28 +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
q3k	d89e1203d9	ca: bump srl	2019-01-13 22:06:11 +01:00
q3k	ae56b6a6a5	clustercfg: create .kubectl	2019-01-13 21:39:16 +01:00
q3k	cd23740185	cluster/secrets: keep plain/ dir for scripting	2019-01-13 21:37:35 +01:00
q3k	de061801db	*: k0.hswaw.net somewhat working	2019-01-13 21:14:02 +01:00
q3k	f2a812b9fd	*: bazelify	2019-01-13 17:51:34 +01:00
q3k	60b19af41e	*: reorganize	2019-01-13 14:15:09 +01:00