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

Signed-off-by: Vegard Hagen <[email protected]>
This commit is contained in:
Vegard Hagen
2025-11-16 19:00:02 +01:00
parent 6f93a2c9d4
commit b73ed2c769
3 changed files with 5 additions and 5 deletions
+3 -3
View File
@@ -12,8 +12,8 @@ spec:
- backendRefs: [ { name: management, port: 80 } ] - backendRefs: [ { name: management, port: 80 } ]
matches: matches:
- headers: [ { name: Content-Type, value: application/grpc } ] - headers: [ { name: Content-Type, value: application/grpc } ]
- method: { service: management.ManagementService } method: { service: management.ManagementService }
- backendRefs: [ { name: signal, port: 10000 } ] - backendRefs: [ { name: signal, port: 80 } ]
matches: matches:
- headers: [ { name: Content-Type, value: application/grpc } ] - headers: [ { name: Content-Type, value: application/grpc } ]
- method: { service: signalexchange.SignalExchange } method: { service: signalexchange.SignalExchange }
@@ -25,7 +25,7 @@ configMapGenerator:
namespace: netbird namespace: netbird
literals: literals:
- LOG_LEVEL="info" - LOG_LEVEL="info"
- DNS_DOMAIN="stonegarden.dev" - DNS_DOMAIN="stonegarden.netbird"
resources: resources:
- deployment.yaml - deployment.yaml
+1 -1
View File
@@ -11,7 +11,7 @@ spec:
- name: http - name: http
port: 80 port: 80
targetPort: http targetPort: http
# appProtocol: kubernetes.io/h2c appProtocol: kubernetes.io/h2c
- name: grpc - name: grpc
port: 10000 port: 10000
targetPort: legacy-grpc targetPort: legacy-grpc