1
0
Fork 0
 
 
 
 
 
 
Go to file
q3k d493ab66ca *: add dcr01s{22,24}
Change-Id: I072e825e2e1d199d9da50b9d38a9ffba68e61182
2019-10-31 17:07:50 +01:00
app Merge "app/radio: add support for following relays" 2019-09-25 12:06:17 +00:00
bgpwtf bgpwtf/internet: fix prod diff 2019-10-11 16:10:14 +02:00
bzl go/{mirko,statusz}: better status, kubernetes client 2019-07-21 23:54:41 +02:00
cluster *: add dcr01s{22,24} 2019-10-31 17:07:50 +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 smsgw: productionize, implement kube/mirko 2019-10-04 13:52:34 +02:00
hswaw hswaw/voucherchecker: detect when voucher is in cart 2019-10-25 19:55:05 +02:00
kube smsgw: productionize, implement kube/mirko 2019-10-04 13:52:34 +02:00
personal/q3k rules_pip: update to new version 2019-09-25 14:05:07 +02:00
third_party/py rules_pip: update to new version 2019-09-25 14:05:07 +02:00
tools *: add dcr01s{22,24} 2019-10-31 17:07:50 +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 Get in the Cluster, Benji! 2019-09-02 16:33:02 +02:00
WORKSPACE dc/arista-proxy: fix by using github.com/q3k/cursedjson 2019-09-26 18:32:39 +02:00
env.sh tools: move cluster-specific stuff to cluster/tools 2019-07-21 14:26:51 +00:00

README

HSCloud
=======

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

You'll also need Nix installed globally in your system until [rules_nixpkgs/75](https://github.com/tweag/rules_nixpkgs/issues/75) is resolved. Or run on NixOS.

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].