[hotfix] Fix namespace for kubelet monitoring (!118)

Co-authored-by: denis.patrakeev <denis.patrakeev@avroid.tech>
Reviewed-on: https://git.avroid.tech/K8s/k8s-configs/pulls/118
Reviewed-by: Rustam Tagaev <rustam.tagaev@avroid.team>
Co-authored-by: Denis Patrakeev <denis.patrakeev@avroid.team>
Co-committed-by: Denis Patrakeev <denis.patrakeev@avroid.team>

clusters/k8s-avroid-office.prod.local/namespaces/kube-prometheus-stack/kube-prometheus-stack/argocd-apps-kube-prometheus-stack-app.yaml

@@ -68,7 +68,3 @@ spec:
       kind: ServiceMonitor
     - group: '*'
       kind: Prometheus
-  # When using Applications-in-any-namespace, this field determines which namespaces this AppProject permits
-  # Applications to reside in. Details: https://argo-cd.readthedocs.io/en/stable/operator-manual/app-any-namespace/
-  sourceNamespaces:
-    - "kube-system"

clusters/k8s-avroid-office.prod.local/namespaces/kube-prometheus-stack/kube-prometheus-stack/values-override.yaml

@@ -25,6 +25,17 @@ alertmanager:
 grafana:
   enabled: false
 
+## Component scraping the kubelet and kubelet-hosted cAdvisor
+##
+kubelet:
+  namespace: kube-prometheus-stack
+
+## Manages Prometheus and Alertmanager components
+##
+prometheusOperator:
+  kubeletService:
+    namespace: kube-prometheus-stack
+
 ## Deploy a Prometheus instance
 ##
 prometheus: