commit | d693a60dc0cc85e9b4f5935ed1828c6e7fe707d8 | [log] [tgz] |
---|---|---|
author | viq <viq@hackerspace.pl> | Sun Jan 07 14:56:38 2024 +0100 |
committer | viq <viq@hackerspace.pl> | Mon Jan 08 20:35:38 2024 +0000 |
tree | a96746ceb0718be5ebf574c3ad69dd43d2671e45 | |
parent | 4d73db2be1fa9ab5e4a8f98565af54cbca422550 [diff] |
cluster/kube/k0.libsonnet: access for viq to monitoring-global-k0 Since `ops/monitoring` operates on both `monitoring-cluster` and `monitoring-global-k0` namespaces, working properly using the tooling requires access to both. While there, add access to `monitoring-external-k0` for potential working with external targets. Change-Id: I5f37ed306f064ffcced705609aa919b684a46235 Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/1834 Reviewed-by: informatic <informatic@hackerspace.pl>
hscloud
is the main monorepo of the Warsaw Hackerspace infrastructure code.
See //doc/codelabs for tutorials on how to use hscloud.
If you want to browse the source of hscloud
in a web browser, use cs.hackerspace.pl.
Initial setup: //doc/codelabs/getting-started/bazel-go.md
Initial bazel build for tools: bazelisk run //tools:install
For additional documentation go to //cluster
If you want some other help, talk to q3k, informatic or your therapist.
Directories you should care about:
k0.hswaw.net
)Unless noted otherwise, code in hscloud is licensed under the BSD 0-clause license - see COPYING.