commit | 99ed6a7abb57ee302a1f2f96c0173f7d0b318d5d | [log] [tgz] |
---|---|---|
author | radex <radex@hackerspace.pl> | Fri Nov 24 11:42:55 2023 +0100 |
committer | radex <radex@hackerspace.pl> | Fri Nov 24 20:38:44 2023 +0000 |
tree | 8d5f95adff9ed0fb3ecfe9b339e2f7aa931b6ade | |
parent | 36964dca3b75e054d24b91dbaec76b0611147e3c [diff] |
kube: standardize on a `local ns` convention A convention is introduced to specify the kube.Namespace object in a deployment as a `local ns` instead of an `ns:` or a `namespace:` for these reasons: - non-cluster admins cannot create new namespaces, and we've been moving in the direction of specifying objects that require cluster admin permissions to apply (policies, role bindings) in //cluster/kube/k0 instead of in the app jsonnet - namespace admins CAN delete the namespace, making `kubecfg delete` unexpectedly dangerous (especially if a namespace contains more than just the contents of the file being applied - common with personal namespaces) - `.Contain()` is a common operation, and it shows up in lines that are pretty long, so `ns.Contain()` is preferable to `app.ns.Contain()` or `service.namespace.Contain()` Change-Id: Ie4ea825376dbf6faa175179054f3ee3de2253ae0 Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/1804 Reviewed-by: q3k <q3k@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.
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.