4
0
Fork 2
mirror of https://gerrit.hackerspace.pl/hscloud synced 2025-02-10 22:46:44 +00:00
hscloud/cluster/prodaccess
Piotr Dobrowolski 1254c9905b bazel: rename io_bazel_rules_go to rules_go
Change-Id: Ib66d48dd4b5eab23c31bb4931855b2f9c7a6d57c
Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/2093
Reviewed-by: q3k <q3k@hackerspace.pl>
Reviewed-by: radex <radex@hackerspace.pl>
2025-01-11 20:40:37 +00:00
..
BUILD.bazel bazel: rename io_bazel_rules_go to rules_go 2025-01-11 20:40:37 +00:00
hspki.go cluster/prodaccess: add multi-cluster support 2025-01-11 15:22:45 +00:00
kubernetes.go cluster/prodaccess: add multi-cluster support 2025-01-11 15:22:45 +00:00
prodaccess.go cluster/prodaccess: add multi-cluster support 2025-01-11 15:22:45 +00:00
README.md cluster/prodaccess: practice proper savoir-vivre 2025-01-08 14:28:11 +00:00

prodvider/prodaccess

It provides access, yo.

Architecture

Prodvider uses an intermediate CA (the prodvider CA, signed by the kube CA), to generate the following:

  • a cert for prodvider to present itself over gRPC for prodaccess clients
  • a cert for prodvider to authenticate itself to the kube apiserver
  • client certificates for prodaccess consumers.

Any time someone runs 'prodaccess', they get a certificate from the intermediate CA, and the intermediate CA is included as part of the chain that they receive. They can then use this chain to authenticate against kubernetes.

Naming

Prodvider customers get certificates with a CN=username@hackerspace.pl and O=sso:username. This means that they appear to Kubernetes as being a User named username@hackerspace.pl and Group named sso:username. In the future, another group might be given to users, do not rely on this relationship.

Kubernetes Structure

After generating a user certificate, prodvider will also call kubernetes to set up a personal user namespace (personal-username), a RoleBinding to system:admin-namespace from their User in their namespace (thus, giving them full rights in it) and a ClusterRoleBinding to system:viewer from their User, thus, giving them some read access for all resources, but not to secure data (like secrets).

system:admin-namespace and system:viewer are defined in //cluster/kube.