Ingress configurator operator

The ingress configurator operator is a Juju charm that acts as a bridge between workloads needing ingress and the route-provider charms that fulfill it. It supports both charm workloads integrating over the ingress interface and external backends described by configuration.

The following route-provider interfaces are supported:

  • haproxy-route and haproxy-route-tcp for HAProxy-based deployments.

  • gateway-route for Kubernetes Gateway API deployments.

In this documentation

Type

General charm documentation

HAProxy

Gateway API integrator

Get started

Deploy the ingress-configurator charm with Gateway API

Operations

Upgrade

Route HTTP traffic to a non-charmed workload | Route TCP traffic to a non-charmed workload | Add HAProxy features to an ingress requirer | Load balance a gRPC server

Add Kubernetes Gateway API features to an ingress requirer | Route traffic for multiple workloads through a single Gateway

Design

Modes of operation

How haproxy-route-tcp works | The cache-config relation

How gateway-route works | The gateway-route relation

How this documentation is organized

This documentation uses the Diátaxis documentation structure.

  • The Tutorial takes you step-by-step through a basic deployment of the Ingress Configurator charm.

  • The How-to guides cover practical tasks for configuring, integrating, and maintaining your deployment.

  • Reference provides technical details on the relation endpoints provided by this charm.

  • Explanation includes context and overviews on modes of operation and how the routing works.

Project and community

The Ingress Configurator operator is a member of the Ubuntu family. It’s an open-source project that warmly welcomes community projects, contributions, suggestions, fixes, and constructive feedback.

Thinking about using the Ingress Configurator operator for your next project? Get in touch!