wip(netbird): don't use legacy grpc port for signal

Signed-off-by: Vegard Hagen <[email protected]>

Author: vehagn

k8s/infra/vpn/netbird/grpc-route.yaml

@@ -12,8 +12,8 @@ spec:
     - backendRefs: [ { name: management, port: 80 } ]
       matches:
         - headers: [ { name: Content-Type, value: application/grpc } ]
-        - method: { service: management.ManagementService }
-    - backendRefs: [ { name: signal, port: 10000 } ]
+          method: { service: management.ManagementService }
+    - backendRefs: [ { name: signal, port: 80 } ]
       matches:
         - headers: [ { name: Content-Type, value: application/grpc } ]
-        - method: { service: signalexchange.SignalExchange }
+          method: { service: signalexchange.SignalExchange }

k8s/infra/vpn/netbird/management/kustomization.yaml

@@ -25,7 +25,7 @@ configMapGenerator:
     namespace: netbird
     literals:
       - LOG_LEVEL="info"
-      - DNS_DOMAIN="stonegarden.dev"
+      - DNS_DOMAIN="stonegarden.netbird"
 
 resources:
   - deployment.yaml

k8s/infra/vpn/netbird/signal/svc.yaml

@@ -11,7 +11,7 @@ spec:
     - name: http
       port: 80
       targetPort: http
-#      appProtocol: kubernetes.io/h2c
+      appProtocol: kubernetes.io/h2c
     - name: grpc
       port: 10000
       targetPort: legacy-grpc