mirror of https://gerrit.hackerspace.pl/hscloud
infra monorepo (https://gerrit.hackerspace.pl)
q3k
09a0f06d2a
Diff against prod:
- live services nginx-system.ingress-nginx
+ config services nginx-system.ingress-nginx
{
"apiVersion": "v1",
"kind": "Service",
"metadata": {
"annotations": {},
"labels": {
"app.kubernetes.io/name": "ingress-nginx",
"app.kubernetes.io/part-of": "ingress-nginx"
},
"name": "ingress-nginx",
"namespace": "nginx-system"
},
"spec": {
- "externalTrafficPolicy": "Cluster",
+ "externalTrafficPolicy": "Local",
"ports": [
{
"name": "ssh",
"port": 22,
"protocol": "TCP",
"targetPort": 22
},
{
"name": "http",
"port": 80,
"protocol": "TCP",
"targetPort": 80
},
{
"name": "https",
"port": 443,
"protocol": "TCP",
"targetPort": 443
}
],
"selector": {
"app.kubernetes.io/name": "ingress-nginx",
"app.kubernetes.io/part-of": "ingress-nginx"
},
"type": "LoadBalancer"
}
}
Change-Id: I0dd66e3f1643efa975d6180cc163a265d4b484ef
|
||
|---|---|---|
| app | ||
| bzl | ||
| cluster | ||
| gcp | ||
| go | ||
| kube | ||
| nix | ||
| proto | ||
| tools | ||
| .bazelrc | ||
| .gitignore | ||
| BUILD | ||
| COPYING | ||
| README | ||
| WORKSPACE | ||
| env.sh | ||
| requirements.txt | ||
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 Kubernets:
echo "185.236.240.36 k0.hswaw.net" >> /etc/hosts # temporary hack until we get loadbalancers working
bazel run //cluster/clustercfg:clustercfg admincreds $(whoami)-admin # get administrative creds (valid for 5 days)
kubectl version
Clusters
========
The following kubernetes clusters are available:
k0.hswaw.net
------------
3 nodes (bc01n{01,02,03}.hswaw.net), mixed worker/master.
No persistent storage (yet).
Temporary development cluster. Will become base production cluster once configuration is done, but will *likely be fully cleared*.
Feel free to use for tests, but your pods might disappear at any time.