Go to file
q3k 114edc2398 kube/mirko: add kube.CephObjectStoreUser
Change-Id: I2a67076eeaf41ada41f5ae3ee588025e4c16b9e1
2020-02-18 22:55:13 +01:00
app {matrix,lelegram}: pin to bc01n0{1,2}.hswaw.net 2020-01-08 13:59:04 +01:00
bgpwtf bgpwtf/invoice: bump for 2020 2020-01-14 14:03:38 +01:00
bzl go/{mirko,statusz}: better status, kubernetes client 2019-07-21 23:54:41 +02:00
cluster kube/mirko: add kube.CephObjectStoreUser 2020-02-18 22:55:13 +01:00
dc dc/arista-proxy: fix by using github.com/q3k/cursedjson 2019-09-26 18:32:39 +02:00
devtools Draw the actual rest of the fucking owl. 2019-08-22 18:14:35 +02:00
gcp secretstore: add implr 2019-05-18 00:15:25 +02:00
go go/{mirko,statusz}: enable profiling 2020-01-23 14:17:30 +01:00
hswaw hswaw/kube/frab: use more unique labels for postgres service 2020-02-15 12:40:25 +01:00
kube kube/mirko: add kube.CephObjectStoreUser 2020-02-18 22:55:13 +01:00
personal/q3k teleimg: fix RE for IRC names 2020-02-02 16:58:57 +01:00
third_party third_party/py: add wtforms 2019-12-19 18:29:45 +01:00
tools env/tools: fix NixOS detection, maybe 2020-02-17 23:04:35 +01:00
.bazelrc smsgw: productionize, implement kube/mirko 2019-10-04 13:52:34 +02:00
.gitignore bgpwtf/cccampix/pgpencryptor: add service base 2019-08-10 10:51:07 -07:00
BUILD *: move away from python_rules 2019-07-16 22:22:05 +00:00
COPYING isc license 2018-10-25 14:25:36 +02:00
README {cluster,}/README: update 2020-02-15 01:00:42 +01:00
WORKSPACE go: bump rules_go, autodetect nix for go toolchains 2020-02-15 01:04:38 +01:00
env.fish env.fish: add 2020-02-15 01:22:58 +01:00
env.sh env/tools: fix NixOS detection, maybe 2020-02-17 23:04:35 +01:00

README

HSCloud
=======

This is a monorepo. You'll need bash and Bazel 1.0.0+ to use it.

If you have Nix installed you will also be able to manage bare metal nodes. If you don't want that, you can skip it.


Getting started
---------------

    cd hscloud
    . env.sh # setup PATH and hscloud_root
    tools/install.sh # build tools


Then, to get Kubernetes access to k0.hswaw.net (current nearly-production cluster):

    prodaccess
    kubectl version

You will automatically get a `personal-$USERNAME` namespace created in which you have full admin rights.

For mor information about the cluster, see [cluster/README].