move archive

archive/gateway-api/manifests/README.md

@@ -0,0 +1,40 @@
+# ------------------------------------------------------------------------------
+# Gateway API CRDs — Standard + Experimental Channel
+# Version: v1.2.1 (latest stable as of May 2026)
+#
+# We reference upstream CRD manifests directly. ArgoCD will apply them
+# from the upstream GitHub URL via the source config in application.yaml.
+#
+# To upgrade Gateway API CRDs:
+#   1. Update the version tag in the URLs below
+#   2. Commit and push — ArgoCD applies automatically
+#
+# Standard channel CRDs (stable, production-ready):
+#   - GatewayClass
+#   - Gateway
+#   - HTTPRoute
+#   - GRPCRoute
+#   - ReferenceGrant
+#
+# Experimental channel additions (used for TCPRoute for non-HTTP services):
+#   - TLSRoute
+#   - TCPRoute
+#
+# Source: https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.2.1
+# ------------------------------------------------------------------------------
+
+# NOTE: ArgoCD applies these from the upstream URL. This file documents
+# the versions in use. The actual application.yaml points ArgoCD at this
+# directory, so place the CRD manifests here by running:
+#
+#   curl -L https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml \
+#     -o cluster/platform/gateway-api/manifests/standard-install.yaml
+#
+#   curl -L https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/experimental-install.yaml \
+#     -o cluster/platform/gateway-api/manifests/experimental-install.yaml
+#
+# Commit both files. ArgoCD will apply them on next sync.
+#
+# The commands above should be run from city-hall or your workstation
+# and the resulting files committed to git. We vendor them rather than
+# fetching at runtime so the exact CRD versions are pinned in git.

archive/gateway-api/manifests/gateway.yaml

@@ -0,0 +1,54 @@
+# ------------------------------------------------------------------------------
+# GatewayClass — tells Kubernetes that Cilium handles Gateway resources
+# Defined here alongside the Gateway it enables
+# ------------------------------------------------------------------------------
+apiVersion: gateway.networking.k8s.io/v1
+kind: GatewayClass
+metadata:
+  name: cilium
+spec:
+  controllerName: io.cilium/gateway-controller
+  description: Cilium Gateway API implementation (eBPF-native)
+
+---
+# ------------------------------------------------------------------------------
+# Gateway — fastpass-gateway
+#
+# This is the central Gateway that all HTTPRoute resources attach to.
+# Cilium operator creates a LoadBalancer service for this Gateway automatically,
+# which will receive an IP from the cilium-gateway-pool (10.1.71.90-.99).
+#
+# Usage: Applications create HTTPRoute resources that reference this Gateway:
+#
+#   spec:
+#     parentRefs:
+#       - name: fastpass-gateway
+#         namespace: gateway-system
+# ------------------------------------------------------------------------------
+apiVersion: gateway.networking.k8s.io/v1
+kind: Gateway
+metadata:
+  name: fastpass-gateway
+  namespace: gateway-system
+  annotations:
+    io.cilium/lb-ipam-ips: "10.1.71.90"
+spec:
+  gatewayClassName: cilium
+  listeners:
+    - name: http
+      protocol: HTTP
+      port: 80
+      allowedRoutes:
+        namespaces:
+          from: All
+    - name: https
+      protocol: HTTPS
+      port: 443
+      allowedRoutes:
+        namespaces:
+          from: All
+      tls:
+        mode: Terminate
+        certificateRefs:
+          - name: argocd-tls
+            namespace: argocd

archive/gateway-api/manifests/namespace.yaml

@@ -0,0 +1,6 @@
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: gateway-system
+  labels:
+    kubernetes.io/metadata.name: gateway-system