Projects and Namespaces
Namespace (Kubernetes concept): "virtual clusters" with separate access control and resource quotas inside the same physical cluster node (they contain workloads, services, configmaps)
Resource names need to be unique within a namespace and namespaces can not be nested inside one another.
Namespaces are used to divide cluster resources and manage permissions between multiple users.
Projects (Rancher Manager concept) help managing clusters by grouping namespaces and to use common configuration.
Projects support multi-tenancy, meaning that for example a team can have access to a project within a cluster without having access to other projects in the same cluster.
If the permissions are restricted to the project level, it is better to create namespaces through Rancher Manager to ensure that the administrator will have proper permissions to access the namespaces.
Clusters contain projects. Projects contain namespaces.
It is possible to move namespaces between projects (restricted by existing quota configuration)
When a cluster is provisioned with Rancher Manager, a project called Default and another called System are automatically created. It can be used to get started with the cluster, but it can always be deleted and replaced.
Main Menu -> Explore cluster -> Cluster Dashboard -> Left menu click Cluster -> Projects / Namespaces