Gateway api support (#890)

* Gateway api support Signed-off-by: Kevin Fox <[email protected]> * Update readme Signed-off-by: Kevin Fox <[email protected]> * Fix gateway name. a gateway doesnt need to be named gateway Signed-off-by: Kevin Fox <[email protected]> * Fix naming issue Signed-off-by: Kevin Fox <[email protected]> * Incorperate feedback Signed-off-by: Kevin Fox <[email protected]> * Incorperate feedback Signed-off-by: Kevin Fox <[email protected]> --------- Signed-off-by: Kevin Fox <[email protected]>
2026-07-30 19:38:43 +00:00
parent 2d92b81ba4
commit 3cfefb72ba
39 changed files with 1015 additions and 5 deletions
@@ -0,0 +1,18 @@
+# Expose the federation bundle endpoint via Gateway API. The federation pod
+# serves a web-PKI cert (externalSecret), so the Gateway uses TLS passthrough
+# (empty gatewayAPI.tlsSecret => TLSRoute + a passthrough SNI listener) and the
+# client validates the pod's cert directly. This is the https_web profile.
+spire-server:
+  tests:
+    tls:
+      enabled: true
+  federation:
+    enabled: true
+    tls:
+      spire:
+        enabled: false
+      externalSecret:
+        enabled: true
+        secretName: spire-server-federation-tls
+    gatewayAPI:
+      enabled: true