https://github.com/robert076/namespaces-practice
Practicing with kubernetes namespaces. Readme contains multiple instructions on how to use the provided files.
https://github.com/robert076/namespaces-practice
k8s kubernetes namespaces
Last synced: 10 months ago
JSON representation
Practicing with kubernetes namespaces. Readme contains multiple instructions on how to use the provided files.
- Host: GitHub
- URL: https://github.com/robert076/namespaces-practice
- Owner: Robert076
- License: apache-2.0
- Created: 2025-06-11T06:42:16.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-06-22T10:23:38.000Z (10 months ago)
- Last Synced: 2025-06-22T10:29:53.027Z (10 months ago)
- Topics: k8s, kubernetes, namespaces
- Homepage:
- Size: 7.81 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 🌎 namespaces-practice
Namespaces are useful for organizing your cluster. The apps you deploy in your cluster should not have any knowledge about what namespace they are on. Namespaces are only for the cluster administrator. You should be able to redeploy an app from namespace A to namespace B without issues.
A good rule of thumb is to have one namespace per microservice. So every resource used in a certain microservice should go in that namespace.
---
### 🚀 Useful commands:
1. Seeing what namespaces you have in your cluster:
```bash
kubectl get ns
```
2. Creating your first namespacet:
```bash
kubectl create ns custom-ns
```
3. Creating a namespace from a file:
```bash
kubectl apply -f custom-ns-2.yml
```
4. Deleting a namespace:
```bash
kubectl delete ns/custom-ns
```
5. Create a resource(eg: configmap) in a certain namespace:
```bash
kubectl create cm configmap-test --from-literal=Lorem=Ipsum -n custom-ns
```
Also, note that you can override the key to the namespaces of the resources that you create declaratively. By adding the -n option to the kubectl create command, you force a namespace as the context for your command: kubectl will take the namespace that was passed in the command into account, not the one present in the YAML file. By doing this, it becomes very easy to duplicate your resources between different namespaces; for example, a production environment in a production namespace and a test environment in a test namespace. The possibilities are endless!
6. Update your default namespace (any cluster):
```bash
kubectl config set-context $(kubectl config current-context) --namespace=robycu
```
7. Get the namespace used by default in your config (only works after you set it manually, by default it is not displayed):
```bash
kubectl config view | grep -i "namespace"
```