In this blog post we will cover the following topics
- Tanzu Mission Control - - Workspaces - - - Creating a workspace - - - Creating a managed Namespace - - - Viewing a managed Namespace - - Policy Driven Cluster Management - - - Creating a Image Registry Policy - - - Creating a Network Policy
The follow up blog posts are;
- Getting Started Tanzu Mission Control - - TMC Resource Hierarchy - - Creating a Cluster Group - - Attaching a cluster to Tanzu Mission Control - - Viewing your Cluster Objects - Cluster Inspections - - Cluster Inspections Overview - - What Inspections are available - - Performing Inspections - - Viewing Inspections - - Data Protection - - - Data Protection Overview - - - Create a AWS Data Protection Credential - - - Enable Data Protection on a Cluster - - - Running a backup manually or via an automatic schedule - - - Restoring your dat
Workspaces provide an application view, where you logically group Kubernetes Namespaces together, regardless of the cluster to which they are attached.
This is in contrast to Cluster Groups, which are focused on the infrastructure view.
These Workspaces can be created to align to your projects or applications, from a hierarchy point of view, you would then authorize your users to these Workspaces, so that they can monitor and manage the namespaces related to their function.
Creating a Workspace
Click the Workspace navigation view on the left-hand side, and then New Workspace.
Specify your Workspace name, and provide the optional description and labels, these can be added after creation if needed.
Now you have a Workspace, it’s no good without any associated Namespaces, so let’s continue.
Creating a managed Namespace
All Namespaces attached to a Workspace will be managed Namespaces under TMC.
To create a managed Namespace, you can do this in one of four places;
- Within the Workspace Navigation view
- Inside the Workspace Object itself
- On the Namespace Navigation view
- On the Cluster Object > Navigation Tab