GatewayAPI Helm Configuration
229
# Gateway API Management Chart
This chart provides a user-friendly way to manage **Gateways** and **HTTPRoutes** using a map-based configuration.
## Default Configuration
The chart comes pre-configured to route traffic for three sample applications. You can view or override these in your `values.yaml`:
```yaml
# CRD installation configuration
crds:
install: false
#Global variable
global:
serviceName: ""
servicePort: ""
#GatewayClass configuration
gatewayClass:
name: nginx
controllerName: gateway.nginx.org/nginx-gateway-controller
description: "NGINX Gateway Fabric controller"
create: true
#Gateway configuration
gateway:
name: my-gateway
namespace: default
gatewayClassName: nginx
listener:
name: http
protocol: HTTP
port: 80
allowedRoutes:
namespaces:
from: All
#HTTPRoute configuration
metadata:
name: app-route
namespace: default
parentRefs: my-gateway
hostnames: []
spec:
rules:
- matches:
- path:
type: PathPrefix
value: /app1
backendRefs:
- name: app1
port: 8080
- matches:
- path:
type: PathPrefix
value: /app2
backendRefs:
- name: app2
port: 8080
- matches:
- path:
type: PathPrefix
value: /
backendRefs:
- name: app3
port: 8080
- matches:
- path:
type: Exact
value: /pod
backendRefs:
- name: server
port: 80
If you only need to change one specific app, you can use the service name directly:
helm install gwapi oci://registry-1.docker.io/srinibat/gateway-api \
--set apps.app-1.path=/new-path \
--set apps.app-1.port=8080
For multiple apps, create a my-apps.yaml and run:
helm install gwapi oci://registry-1.docker.io/srinibat/gateway-api -f my-apps.yaml
README.md in your C:\Kubernetes\helm-charts\gateway-api\ folder.Chart.yaml version to 0.1.5.helm package .
helm push gateway-api-0.1.5.tgz oci://registry-1.docker.io/srinibat
Content type
Helm
Digest
sha256:6f20283ce…
Size
100.8 kB
Last updated
9 months ago
helm pull oci://registry-1.docker.io/srinibat/gateway-api --version 0.1.4