Automating tenant onboarding

Earlier, in the vCluster chapter, we deployed the OpenUnison NaaS portal to provide a self-service way for users to request tenants and have them deployed. This portal lets users request new namespaces to be created and allows developers to request access to these namespaces via a self-service interface. We built on this capability to include the creation of a vCluster in our namespace in addition to the appropriate RoleBinding objects. While that implementation was a good start, it ran everything on a single cluster and only integrated with the components that were needed to run a vCluster.

What we want to do is build a workflow that integrates our platform and creates all the objects we need to fulfill our requirements across all of our projects. The goal is that we’ll be able to deploy a new application into our environment without having to run the kubectl command (or at least minimize its use).

This will require careful planning. Here...