Fix brusnika-stage observability bootstrap ordering

clusters/brusnika-stage/infrastructure/kustomization.yaml

@@ -15,7 +15,6 @@ resources:
   - ../../../infrastructure/goalert
   - ../../../infrastructure/kafka-exporter
   - ../../../infrastructure/postgres-exporter
-  - ./node-exporter-vmnodescrape.yaml
   - ./lb-service-override.yaml
   - ./vault-ingress.yaml
   - ./clusterissuer-letsencrypt.yaml

clusters/brusnika-stage/infrastructure/node-exporter-vmnodescrape.yaml

@@ -1,20 +0,0 @@
-apiVersion: operator.victoriametrics.com/v1beta1
-kind: VMNodeScrape
-metadata:
-  name: vm-stage-node-exporter
-  namespace: vmstack
-spec:
-  path: /metrics
-  port: "9100"
-  scheme: http
-  selector: {}
-  relabelConfigs:
-    - action: labelmap
-      regex: __meta_kubernetes_node_label_(.+)
-    - action: replace
-      sourceLabels:
-        - __meta_kubernetes_node_name
-      targetLabel: node
-    - action: replace
-      replacement: brusnika-stage/vm-node-exporter
-      targetLabel: job