hscloud/cluster
q3k 3d29484ebb k0: move registry to ceph-waw3
ceph-waw2 has currently some production issues [1] which have started to
cause write failures in the registry. The registry is the only user of
ceph-waw2's affected pool, so we reduce the dumpster fire blast radious
by moving it over to ceph-waw3.

This has already been deployed and data has been migrated over (via
s3cmd sync), and the migration has been verified (by a push and pull,
and pull of an older image).

[1] - pgs stuck inactive in the object storage pool

Change-Id: I26789b52008bb7be953954ec3fd3dd727ac15347
2020-08-04 01:36:51 +02:00
..
certs cluster: bump nearly-expired certs 2020-03-28 18:01:40 +01:00
clustercfg Replace rules_pip with rules_python; use bazel built upstream grpc 2020-07-08 18:55:34 +02:00
doc cluster/kube: split up cluster.jsonnet 2020-06-13 19:51:58 +02:00
kube k0: move registry to ceph-waw3 2020-08-04 01:36:51 +02:00
nix cluster: bump kubelets to 1.14.3 2020-02-02 23:43:28 +01:00
prodaccess *: developer machine HSPKI credentials 2020-08-01 17:15:52 +02:00
prodvider prodvider: emit client/server cert 2020-08-01 22:01:05 +02:00
secrets tools/secretstore: add sync command, re-encrypt 2020-06-04 19:25:07 +00:00
tools cluster/tools/rook-s3cmd-config: build using bazel 2020-06-13 22:46:41 +02:00