This message was deleted.
# kubernetes
a
This message was deleted.
đź‘€ 1
c
No. There is a namespace for every user and project, to hold settings specific to those items.
when the user or project is deleted, so is the namespace.
p
is there a way to not have those namespaces created for each user/project? I see a rancher also makes project and user/userattributes objects which contain the actual settings where as the namespace doesn't contain any additional info? We have several teams that apparently all need access to the RKE2 cluster which leads to us having to scroll scroll past many, many u- namespaces
Copy code
apiVersion: v1
kind: Namespace
metadata:
  annotations:
    <http://cattle.io/status|cattle.io/status>: '{"Conditions":[{"Type":"ResourceQuotaInit","Status":"True","Message":"","LastUpdateTime":"2024-11-26T15:38:11Z"},{"Type":"InitialRolesPopulated","Status":"True","Message":"","LastUpdateTime":"2024-11-26T15:38:11Z"}]}'
    <http://lifecycle.cattle.io/create.namespace-auth|lifecycle.cattle.io/create.namespace-auth>: "true"
  creationTimestamp: "2024-11-26T15:38:10Z"
  finalizers:
  - <http://controller.cattle.io/namespace-auth|controller.cattle.io/namespace-auth>
  labels:
    <http://kubernetes.io/metadata.name|kubernetes.io/metadata.name>: u-5du3l4pat5
  name: u-5du3l4pat5
  resourceVersion: "581289535"
  uid: 67a16833-370a-4799-ba6c-9d12df0fdfb9
spec:
  finalizers:
  - kubernetes
status:
  phase: Active
c
no
You’re not supposed to give folks access to the rancher local cluster, or let them poke at the system namespaces. End users should access and manage downstream clusters.
User-facing workloads shouldn’t be deployed to the rancher local cluster either.
the rancher local cluster is supposed to be for Rancher only.