Skip to content

Installing management plane

Superphenix is installed through an operator running on the management cluster. The operator installs each Superphenix cluster from the configuration in its Cluster resource, and it owns installation, upgrades, and lifecycle for those clusters.

On the management cluster itself, the operator installs ArgoCD and a Cluster of type Management. That cluster pulls the management applications from the superphenix-system chart:

  • The Superphenix web console, API, Kratos, and Permify
  • PostgreSQL, shared by the API, Kratos, and Permify
  • The Talos operator and the iDRAC exporter, both optional and disabled by default

Storage for the database and ingress for HTTP are not part of that management set. They have to exist on the management cluster. When management runs inside an AZ, they arrive with the local AZ. See Configuring the management stack.

The default local AZ

The system chart registers one AZ with the API under the code local, displayed as Local AZ.

That entry is the hyperconverged AZ that shares the management cluster. Install it with the operator chart key clusters.local, as described in Installing hyperconverged.

When this management cluster should not run an AZ, disable that default. Set local to null in the API configuration, and do not set clusters.local:

management:
  systemConfiguration:
    apps:
      superphenix-api:
        values:
          config:
            azs:
              local: null
            productsConfig:
              argoApp:
                kubernetes:
                  azDomains:
                    local: null

Installing outside an AZ uses this override. Add an availability zone covers registering every other AZ with the API and its controller.

Next steps