Apicurio Registry Installation
This guide introduces the Apicurio Registry part of a streaming installation: switching the registry on in the Axual Streaming chart, choosing how clients authenticate against it, and adding the Auth Proxy when clients arrive with both OAuth tokens and Basic Auth credentials. For what Apicurio Registry is and how it stores schemas, see Apicurio Registry.
Type |
Reference |
Goal |
Find the guide needed to enable Apicurio Registry and set up how its clients authenticate. |
Audience |
Platform Operators who can edit the Axual Streaming values and apply them. |
When to use |
Part of stage 3 of The installation order, after the streaming chart exists and before Governance Installation. |
The pages below cover the registry in the order it is set up:
-
How to Enable Apicurio Registry switches Apicurio Registry v3 on, applies a working base configuration, and checks the registry answers over TLS.
-
Apicurio Registry Read Access Models compares anonymous reads against authenticated reads, so the choice comes before the values that apply it.
-
How to Configure Apicurio Authentication moves the registry off its default anonymous read access onto Keycloak-backed roles.
-
How to Enable the Apicurio Auth Proxy adds the sidecar that accepts OAuth and Basic Auth at the same time, which the registry cannot do on its own.
Every value the registry accepts is listed beside the component’s other details, in Apicurio Chart Values Reference.
The registry is enabled from the streaming values file, so Install Axual Streaming comes first. Stage 3 is finished once the registry answers, so complete these pages before stage 4, Governance Installation. When the registry pod runs but clients cannot reach it, start from Troubleshooting.