Why are namespaces created via the kubectl CLI not assigned to a project?
This document (000020218) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Rancher 2.7.x
SUSE Rancher 2.8.x
SUSE Rancher 2.8.x
Situation
When a user creates a Kubernetes namespace via the Rancher UI, API or CLI the namespace is created within a specified Rancher project in the cluster; however, when a user creates a namespace via the kubectl CLI (kubectl create ns <namespace>) it is created outside of any project, why is this?
Resolution
- If you want to create namespaces within a Rancher Project with a command-line tool, then you should use the Rancher CLI (https://rancher.com/docs/rancher/v2.x/en/cli/ ) OR cluster admin can move the namespace into a project, within the 'Projects/Namespaces' view for the cluster.
Cause
- It is expected behavior that namespaces created via the kubectl CLI are created outside of a Project.
- Projects are Rancher abstractions and do not exist natively within Kubernetes, as a result when you create a namespace via the kubectl CLI, it is not associated with any project in Rancher.
- Projects are Rancher abstractions and do not exist natively within Kubernetes, as a result when you create a namespace via the kubectl CLI, it is not associated with any project in Rancher.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020218
- Creation Date: 06-May-2021
- Modified Date:22-Jul-2024
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
