docs: Update namespace on migrating from Cluster Autoscaler guide (#8094)

Author: engedaam

website/content/en/docs/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/preview/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/v0.32/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/v1.0/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/v1.2/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/v1.3/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed

website/content/en/v1.4/getting-started/migrating-from-cas/_index.md

@@ -188,7 +188,7 @@ If you have a lot of nodes or workloads you may want to slowly scale down your n
 As nodegroup nodes are drained you can verify that Karpenter is creating nodes for your workloads.
 
 ```bash
-kubectl logs -f -n karpenter -c controller -l app.kubernetes.io/name=karpenter
+kubectl logs -f -n "${KARPENTER_NAMESPACE}" -l app.kubernetes.io/name=karpenter -c controller
 ```
 
 You should also see new nodes created in your cluster as the old nodes are removed