Using namespaces to limit access
The Hue project is moving along nicely, and we have a few hundred microservices and about 100 developers and DevOps engineers working on it. Groups of related microservices emerge, and you notice that many of these groups are pretty autonomous. They are completely oblivious to the other groups. Also, there are some sensitive areas such as health and finance that you want to control access to more effectively. Enter namespaces.
Let’s create a new service, Hue-finance, and put it in a new namespace called restricted.
Here is the YAML file for the new restricted namespace:
kind: Namespace
apiVersion: v1
metadata:
name: restricted
labels:
name: restrictedWe can create it as usual:
$ kubectl create -f restricted-namespace.yaml
namespace "restricted" createdOnce the namespace has been created, we can configure a context for the namespace.
$ k config set-context k3d-k3s-restricted --cluster k3d-k3s-default --namespace=restricted...