Axual Connect Installation

This reference lists the guides that make up the Axual Connect part of a runtime installation: installing the chart, adding connector plugins and offering them to App Owners, hosting the archives the workers download at startup, and getting connector logs into Self-Service. For what Axual Connect is, see Axual Connect.

Type

Reference

Goal

Find the guide needed to install or maintain an Axual Connect deployment.

Audience

Platform Operators with Helm access to the namespace, plus a Tenant Admin account for the Self-Service steps.

When to use

Part of stage 5 of The installation order, on an installation that already runs Axual Connect.

Axual Connect is deprecated (see Why Kafka Connect replaces Axual Connect for the timeline). A new installation deploys Kafka Connect instead, which gives each tenant its own Strimzi-managed cluster rather than one cluster shared by every tenant on the instance. An installation already running Axual Connect moves across with Migrating from Axual Connect to Kafka Connect.

The pages below cover Axual Connect in the order it is set up:

How to Deploy Axual Connect prepares the governance values, installs the chart, and switches Axual Connect on for an instance in Self-Service.
How to Install Connect Plugins packages a connector plugin and points Axual Connect at the archive.
How to Publish Connect Plugins to Self-Service gets an installed plugin offered to App Owners.
How to Host a Plugin Download Location serves those archives from somewhere the workers can reach.
Enabling Connector Logging into Kafka makes connector logs for an instance visible in Self-Service.

Vault comes first, because the governance values reference the AppRole it holds: see How to Set Up Vault for Axual Connect. Nothing in the installation depends on Axual Connect, so the remaining stage 5 components can be installed in any order. When a worker starts but a connector does not run, start from Troubleshoot an Axual Connect Deployment.