How-to guides¶
Manage the full operations lifecycle of the Gateway API integrator charm, from configuring a GatewayClass and publishing routes through TLS hardening and maintenance. Each guide assumes that you have already deployed the charm with Juju.
Traffic routing and endpoints¶
The charm manages Gateway and HTTPRoute resources to expose workloads through a gateway controller. These guides cover selecting the controller to bind to, configuring the hostname for backend applications, sharing one Gateway across several backends, and inspecting the public URLs for each backend.
Select a gateway class: Bind the
Gatewayresource to aGatewayClasssupplied by a controller installed on the cluster.Configure the external hostname: Set the FQDN served through the
ingressrelation and used for the listener, certificate, published URL, and DNS records.Route traffic to multiple workloads: Share a single Gateway across several backends by deploying one
ingress-configuratorapplication per route.Get proxied endpoints: Run the
get-proxied-endpointsaction to retrieve the gateway and application URLs.
TLS and transport security¶
The charm enforces HTTPS by default, so it requires a certificate provider and redirects plain HTTP to HTTPS. These guides cover supplying the TLS certificates via a provider charm, adjusting HTTPS enforcement, and tuning the policy that browsers apply after reaching the hostname over HTTPS.
Provide a certificate: Integrate a TLS provider such as
self-signed-certificates,manual-tls-certificates, or LEGO to satisfy thecertificatesrelation.Configure HTTPS enforcement: Keep or turn off the default HTTP-to-HTTPS redirect, and control whether an HTTPS listener is created.
Configure HSTS: Set the
Strict-Transport-Securitymax-agethat browsers apply to the hostname.
Maintenance and development¶
Upgrades and community contributions ensure the Gateway API Integrator charm stays current and benefits from ongoing improvements.
Upgrade: Refresh the charm to a newer revision or channel with
juju refresh.Contribute: Set up a development and documentation workflow to build the charm, run tests, and submit improvements.