Skip to content

v0.25.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Sep 05:46
· 9 commits to main since this release
v0.25.5
a00627e

Image: 1kcsd/devops-tools:0.25.5
Chart version: 0.28.0

What changed

  • The chart now grants the service account every resource by default
    (rbac.fullAccess). Removing a Helm release means deleting whatever that
    release created, and rolling one back means creating it again — a list of
    kinds stops being enough the moment a chart carries an operator's custom
    resource, and then the uninstall halts half-way, leaves the release behind
    and says only that it failed. Argo CD and Flux grant their controllers the
    same thing for the same reason. With rbac.scope: cluster this makes the
    service account a cluster administrator: it does not change what the portal
    offers anyone — that is the access model's decision — but the token in the
    pod becomes a cluster-admin credential. Set rbac.fullAccess: false for the
    previous list of kinds. An upgrade widens an existing installation's
    permissions    , which is worth knowing before taking it.
  • A failed Helm operation now says what went wrong. Which resource could not
    be deleted is something the SDK narrates in passing and leaves out of the
    error it returns, so the audit trail recorded "failed" and nothing else — and
    a half-removed release could sit unnoticed for a fortnight. That detail is
    carried out now, into the message on screen and into the trail.
  • config.logLevel: debug, info, warn or error. Worth having because some
    of what the service knows was written at debug and therefore unreachable at
    any setting.
  • The role editor reads as the three questions it asks. The buttons that add a
    namespace or a configuration path sat between two blocks, close enough to the
    next heading to look like part of it; they now continue the list they add to,
    and a rule separates the sections.
  • The Storage tab no longer moves the Users / Roles / Storage switcher down a
    line when you reach it.
  • The post-install notes said the default account was admin / admin. It has
    not been since the chart stopped shipping a password.

Install

Start from an example values file — one per way of signing in:

# accounts kept by the portal itself, with nothing else to install
curl -O https://raw.githubusercontent.com/kcsd-labs/devops-tools/v0.25.5/examples/values-local.yaml
# Active Directory or OpenLDAP
curl -O https://raw.githubusercontent.com/kcsd-labs/devops-tools/v0.25.5/examples/values-ldap.yaml
# Keycloak, and anything else speaking OpenID Connect
curl -O https://raw.githubusercontent.com/kcsd-labs/devops-tools/v0.25.5/examples/values-oidc.yaml

Fill in the one you took, then install with it:

helm install devops-tools oci://registry-1.docker.io/1kcsd/devops-tools --version 0.28.0 \
  --namespace devops-tools --create-namespace \
  -f values-ldap.yaml

The administrator password is the one thing an install has to decide:
nothing here ships a default, so with none set the service stops at
startup rather than coming up as a portal anybody could walk into.

Assets 2
Loading