Migrate HTTPRoute to Helm charts #455
Description
Phase 1: Find Candidates
Applications with standalone HTTPRoute manifests or disabled ingress with upstream Helm charts:
Active:
- ArgoCD (
manifests/argocd/httproute.yaml) - Longhorn (
manifests/longhorn/httproute.yaml) - Grafana Operator (
manifests/grafana-operator/httproute.yaml) - Victoria Metrics (ingress disabled in values, needs HTTPRoute support)
Disabled:
- Kubernetes Dashboard (
argocd-disabled/dashboard.yaml- Traefik Ingress, needs Gateway API) - Jellyfin (
argocd-disabled/jellyfin.yaml- Traefik Ingress, needs Gateway API) - Loki Stack (
argocd-disabled/loki-stack.yaml- no ingress, needs Gateway API)
Already migrated:
- me-site (HTTPRoute configured via Helm values ✓)
Phase 2: Upstream PRs
- feat(argo-cd): Add HTTPRoute support for Gateway API argoproj/argo-helm#3517
- feat(argo-workflows): Add Gateway API HTTPRoute support argoproj/argo-helm#3567
- feat(chart): add Gateway API HTTPRoute support kyverno/policy-reporter#1238
- feat(chart): add Gateway API HTTPRoute support longhorn/longhorn#11911
- feat(ingress): add HTTPRoute support for Grafana instances grafana/grafana-operator#2283
- Victoria Metrics
- Add Gateway API HTTPRoute support to Helm chart kubernetes/dashboard#10385
- feat(gateway-api): add HTTPRoute support jellyfin/jellyfin-helm#86
- feat(helm): add HTTPRoute support for Gateway API v1 grafana/loki#19729
Phase 3: Internal Migration
- ArgoCD
- Argo Workflows
- Longhorn
- Grafana Operator
- Victoria Metrics
- Kubernetes Dashboard
- Jellyfin
- Loki Stack
- Kyverno policy-reporter