From c7978ea97da8e4c00eb75d98b85fae2e6473b6eb Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Tue, 16 Nov 2021 15:45:10 -0500 Subject: [PATCH] Updated wording per feedback --- .../v2.6/en/cluster-admin/projects-and-namespaces/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/cluster-admin/projects-and-namespaces/_index.md b/content/rancher/v2.6/en/cluster-admin/projects-and-namespaces/_index.md index cd309190b93..79fc054dc21 100644 --- a/content/rancher/v2.6/en/cluster-admin/projects-and-namespaces/_index.md +++ b/content/rancher/v2.6/en/cluster-admin/projects-and-namespaces/_index.md @@ -8,7 +8,7 @@ A namespace is a Kubernetes concept that allows a virtual cluster within a clust A project is a group of namespaces, and it is a concept introduced by Rancher. Projects allow you to manage multiple namespaces as a group and perform Kubernetes operations in them. You can use projects to support multi-tenancy, so that a team can access a project within a cluster without having access to other projects in the same cluster. ->**Note:** As of Rancher v2.6, projects are de-emphasized on the UI because you don't need them anymore to create secrets exclusively. However, it's still possible to create [secrets in projects]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/#creating-secrets-in-projects) if desired. +>**Note:** As of Rancher v2.6, projects are de-emphasized on the UI because it is no longer required to create any Kubernetes resources within a project scope. However, resources such as [Secrets]({{}}/rancher/v2.6/en/k8s-in-rancher/secrets/#creating-secrets-in-projects) can still be created in a project scope if the legacy feature flag is enabled. This section describes how projects and namespaces work with Rancher. It covers the following topics: