feat(gateway-api): add HTTPRoute support
Add support for Kubernetes Gateway API HTTPRoute resource as a modern alternative to Ingress. The implementation follows the same pattern as the existing Ingress template. Changes: - Add HTTPRoute template with configurable parentRefs, hostnames, and rules - Add httpRoute section to values.yaml with generic examples - Update Chart version from 2.5.0 to 2.6.0 - Add Artifact Hub changelog annotation - Add HTTPRoute documentation to README Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
This commit is contained in:
1 parent
2401a45bb1
commit
f1ae87fba9
5 files changed
+116
-2
No files matched your search
@@ -124,6 +124,25 @@ ingress:
|
||||
# hosts:
|
||||
# - chart-example.local
|
||||
|
||||
# -- HTTPRoute configuration for Gateway API. See: https://gateway-api.sigs.k8s.io/
|
||||
httpRoute:
|
||||
enabled: false
|
||||
annotations: {}
|
||||
# -- Gateway references to attach this HTTPRoute to
|
||||
parentRefs: []
|
||||
# - name: my-gateway
|
||||
# namespace: gateway-system
|
||||
# sectionName: https
|
||||
# -- Hostnames to match for this HTTPRoute
|
||||
hostnames: []
|
||||
# - jellyfin.example.com
|
||||
# -- Rules for routing traffic
|
||||
rules:
|
||||
- matches:
|
||||
- path:
|
||||
type: PathPrefix
|
||||
value: /
|
||||
|
||||
# -- Resource requests and limits for the Jellyfin container.
|
||||
resources: {}
|
||||
# limits:
|
||||
|
||||
Reference in new issue
Block a user