Files
cozystack/packages/system/linstor-gui
Alexey Artamonov 80d32b3ab7 fix(keycloak): complete realm-name coverage and guard non-string names
The enable-update-email hook Job in keycloak-configure still pinned
REALM=cozy, so on a custom realmName it waited on a realm the chart never
provisions and the cold install timed out — the one seventh consumer left
behind, and the only value nobody could set without breaking the install.

A bare-integer or YAML-reserved realm name reached the printf %s that
builds the derived keycloakInternalUrl as a Go int, rendering a
"%!s(...)" format error into the URL; coerce the name to a string once
at the source.

Document that renaming the realm on a running cluster provisions a fresh
empty realm and orphans the accounts in the old one, and note in the OIDC
tenant and grafana guides that the realm name is now the configurable
default. info/Makefile carried NAME=etcd, so cozyhr drove the wrong
release from that package; correct it while touching the file.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
2026-09-21 12:15:10 +03:00
..

linstor-gui

Cozystack system package for LINBIT/linstor-gui — a web UI for managing LINSTOR nodes, resources, volumes and snapshots.

Installed alongside the linstor package in the cozy-linstor namespace. The UI proxies the LINSTOR controller REST API at https://linstor-controller.cozy-linstor.svc:3371 using mTLS with the linstor-client-tls secret created by the linstor package.

Exposing the UI

The chart ships an oauth2-proxy based gatekeeper plus a KeycloakClient CRD so the UI can be published on linstor-gui.<root-host> behind the cluster Keycloak realm. Access is restricted to members of the cozystack-cluster-admin Keycloak group — the same group that grants cluster-admin RBAC on the host cluster. Authenticating against the cozy realm alone is not sufficient; users outside that group receive a 403 from oauth2-proxy before any request reaches the UI or the LINSTOR controller.

To turn it on, add linstor-gui to publishing.exposedServices in the core cozystack values (same list that controls dashboard). OIDC must be enabled (authentication.oidc.enabled: true) — if it is not, the Ingress and gatekeeper Deployment are deliberately not rendered, because the LINSTOR REST API surface must not be exposed unauthenticated.

Once enabled, the UI is reachable at https://linstor-gui.<root-host> and authentication is delegated to Keycloak via the linstor-gui client (auto-provisioned through the KeycloakClient CRD; the client secret is persisted in the linstor-gui-client Secret in cozy-linstor).

Option 2 — Port-forward

If you have not set up Keycloak or want ad-hoc access, use the ClusterIP Service:

kubectl -n cozy-linstor port-forward svc/linstor-gui 3373:80

then open http://localhost:3373.

Parameters

Image

Name Description Value
image.repository LINSTOR GUI container image repository ghcr.io/cozystack/cozystack/linstor-gui
image.tag LINSTOR GUI container image tag (digest recommended) 2.3.0

Deployment

Name Description Value
replicas Number of linstor-gui replicas 1

LINSTOR controller connection

Name Description Value
linstor.endpoint In-cluster URL of the LINSTOR controller REST API (HTTPS, mTLS) https://linstor-controller.cozy-linstor.svc:3371
linstor.clientSecret Kubernetes Secret with tls.crt, tls.key, ca.crt used as the mTLS client certificate against the LINSTOR controller. Created by the linstor package. linstor-client-tls