Ingress configurator operator

A Juju charm that serves as a translation layer between the ingress interface and route-provider interfaces.

It currently supports:

• haproxy-route and haproxy-route-tcp
• gateway-route (adapter mode on Kubernetes)

Like any Juju charm, this charm supports one-line deployment, configuration, integration, scaling, and more.

For information about how to deploy, integrate, and manage this charm, see the Official Ingress configurator operator documentation.

Get started

Basic operations

The ingress-configurator charm supports two workflows.

• Ingress relation workflow: a workload charm relates over ingress, and ingress-configurator forwards the routing requirements to a route provider.
• Config-driven workflow: non-charm workloads are described by config and routed through route-provider relations. The following configurations must be set:
  • backend-addresses
  • backend-ports

HAProxy

HAProxy is supported through the haproxy-route or the haproxy-route-tcp relation.

• haproxy-route supports both the ingress relation and config-driven workflows.
• haproxy-route-tcp supports the config-driven workflow only.
• Supports a broad set of haproxy-route related configurations:
  • paths
  • subdomains

Gateway API

Gateway API is supported through the gateway-route relation.

• Supports the ingress relation workflow only; config-driven backends are not supported.
• Requires that the backend related through ingress has opened its ports.
• https option for backend-protocol is not supported.

To obtain the full list of configurations, see the official CharmHub documentation.

Learn more

• Read more
• Troubleshooting

Project and community

• Issues
• Contributing
• Matrix