From fa2b428c560537f3252041a8b0a6f08533894e53 Mon Sep 17 00:00:00 2001
From: Dario Tranchitella <dario@tranchitella.eu>
Date: Mon, 9 May 2022 14:49:47 +0200
Subject: [PATCH] docs(proxy): documenting retrieval of a single namespace

---
 docs/content/general/proxy.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/docs/content/general/proxy.md b/docs/content/general/proxy.md
index 291511b5..6a4d13de 100644
--- a/docs/content/general/proxy.md
+++ b/docs/content/general/proxy.md
@@ -30,7 +30,7 @@ The `capsule-proxy` implements a simple reverse proxy that intercepts only speci
 Current implementation filters the following requests:
 
 * `/api/scheduling.k8s.io/{v1}/priorityclasses{/name}`
-* `/api/v1/namespaces`
+* `/api/v1/namespaces{/name}`
 * `/api/v1/nodes{/name}`
 * `/api/v1/pods?fieldSelector=spec.nodeName%3D{name}`
 * `/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/{name}`
@@ -151,6 +151,21 @@ oil-development     Active   2m
 oil-production      Active   2m
 ```
 
+Capsule Proxy supports applying a Namespace configuration using the `apply` command, as follows.
+
+```
+$: cat <<EOF | kubectl apply -f -
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: solar-development
+EOF
+
+namespace/solar-development unchanged
+# or, in case of non existing Namespace:
+namespace/solar-development created
+```
+
 ### Nodes
 
 The Capsule Proxy gives the owners the ability to access the nodes matching the `.spec.nodeSelector` in the Tenant manifest: