Feature Request: Support Gateway API

[volker-raschek]

Description

The current Helm chart for ChartMuseum does not support the Kubernetes Gateway API specification. At the moment, exposure of the service is primarily focused on traditional Ingress resources.

As the Gateway API is becoming the successor and modern alternative to the Ingress API, it would be very beneficial if the Helm chart supported deployment and configuration of Gateway API resources natively.

Expected Behavior

The Helm chart should provide optional support for:

• Gateway
• HTTPRoute
• configurable listeners / hostnames
• integration with existing GatewayClass implementations

Ideally, this support would be configurable similarly to the current Ingress configuration via values.yaml.

Example configuration ideas:

route:
  enabled: false
  apiVersion: gateway.networking.k8s.io/v1
  kind: HTTPRoute
  annotations: {}
  labels: {}
  hostnames: []
  parentRefs: []
  httpsRedirect: false
  matches:
  - path:
      type: PathPrefix
      value: /
  filters: []
  sessionPersistence: {}
  additionalRules: []

Motivation

Many Kubernetes environments are moving towards Gateway API adoption because it offers:

• better separation of concerns
• improved extensibility
• richer traffic management capabilities
• standardized API evolution

Without native support, users currently need to create and manage Gateway API manifests separately from the Helm release, which reduces deployment consistency and increases operational overhead.

Additional Context

Gateway API is now widely supported by multiple ingress/controller implementations such as:

• Istio
• Traefik
• Kong
• Cilium
• NGINX Gateway Fabric

Adding support would modernize the chart and improve compatibility with current Kubernetes networking standards.