The DAWO workplace stack (LDAP, Sextant, NetBird, Zitadel) as Fundament plugins https://github.com/fundament-oss/fundament
  • Go 79.5%
  • Shell 15.9%
  • Dockerfile 1.8%
  • Python 1.8%
  • Just 1%
Find a file
Bram Buijs ed5504c29f
All checks were successful
ci / check (push) Successful in 3m30s
hack/freeipa-probe: measure the cgroup mount, record the kind run
A local run on kind (containerd) shows systemd starts as PID 1 but cannot
write /sys/fs/cgroup, so it starts no units and ipa-server-install never
begins. The probe now prints the cgroup mount and stops after three minutes
without a systemd bus instead of waiting twenty.
2026-11-16 11:07:52 +00:00
.forgejo/workflows ci: push only, on the build host, in a Go container 2026-11-12 17:32:23 +00:00
docs hack: FreeIPA feasibility probe for the fieldlab 2026-11-14 21:26:32 +00:00
hack hack/freeipa-probe: measure the cgroup mount, record the kind run 2026-11-16 11:07:52 +00:00
internal fix(netpol): sextant and netbird may reach the Gateway's pods 2026-11-12 20:21:31 +00:00
plugins sextant: push console commits to an overlay remote (v0.1.2) 2026-11-13 23:02:55 +00:00
services/device-login chore: publish under forgejo.bb-open.com/bbopen 2026-11-12 17:10:01 +00:00
.gitignore feat: shared plugin layer and the Sextant plugin 2026-11-04 21:14:40 +01:00
go.mod chore: publish under forgejo.bb-open.com/bbopen 2026-11-12 17:10:01 +00:00
go.sum feat(netbird): the NetBird mesh plugin 2026-11-04 21:43:39 +01:00
Justfile chore: publish under forgejo.bb-open.com/bbopen 2026-11-12 17:10:01 +00:00
LICENSE feat: shared plugin layer and the Sextant plugin 2026-11-04 21:14:40 +01:00
README.md chore: publish under forgejo.bb-open.com/bbopen 2026-11-12 17:10:01 +00:00

fundament-plugins

The DAWO workplace stack as Fundament plugins: a directory (ldap), the fleet control plane (sextant), a mesh (netbird) and an identity provider (zitadel). Each one stands on its own: the directory serves any identity provider, the console takes any OIDC issuer and any LDAPS directory, the mesh takes any OIDC issuer. Together they are the DAWO stack; apart they are four marketplace apps. First used at the Fieldlab Soevereine Basis, 23–25 November 2026.

Plugin What it installs Needs from the operator
ldap OpenLDAP, LDAPS only, its own CA, one read-only account per consumer (BIND_ACCOUNTS), optional demo people nothing; see docs/handoff-ldap.md for Zitadel, Keycloak, Sextant and SSSD
sextant The Sextant console with an embedded Postgres; OIDC and LDAP when configured sextant-oidc, sextant-ldap, sextant-ldap-ca Secrets when those are on
netbird NetBird management, signal, relay and dashboard on one hostname behind the cluster's Gateway; login through NetBird's own identity provider or any OIDC issuer nothing; see docs/handoff-netbird.md
zitadel Zitadel with its own Postgres, a first organisation, an administrator and an API token; login v1 or v2 behind the cluster's Gateway nothing; see docs/handoff-zitadel.md for the Secrets it leaves and the LDAP and device sign-on providers

Where it lives

  • Source: https://forgejo.bb-open.com/bbopen/fundament-plugins
  • Images, public, no login needed: forgejo.bb-open.com/bbopen/<name>
    • sextant-plugin, ldap-plugin, netbird-plugin, zitadel-plugin: the plugins
    • device-login: the bridge for sign-on from the device (docs/sso-from-device.md)
    • openldap-rootless: the directory the ldap plugin runs
    • sextant: the Sextant console the sextant plugin installs (with its -tools tag); Sextant's source is mirrored at https://codeberg.org/DAWO/DAWO-Sextant

The tags are in docs/demo-script.md; every plugin is pinned by digest in the marketplace, never by tag.

How a plugin here is built

Every plugin is a small Go binary on the Fundament plugin SDK that installs a Helm chart baked into its own image, into its own namespace, and keeps it healthy. The shared pieces are in internal/:

  • helm: runs the helm CLI without --create-namespace, so no plugin needs a cluster-wide right. Values go through a private file, never --set.
  • secrets: generates what can be generated, never overwrites, never logs.
  • pki: a CA and server certificates per installation; the CA is published in a ConfigMap, because a consumer needs it and it is not secret.
  • netpol: default-deny on the plugin namespace plus the allow rules.
  • kube: own namespace, client, readiness.

spec.permissions.rbac is empty in every definition.yaml, and a test fails if it stops being empty.

Secrets

Fundament has no secret input for plugins: spec.config is a plain field readable by anyone who can read the installation. So a plugin generates its own secrets in-cluster and reports, in its status, the name of the Secret an operator still has to create and what it must contain. Handing a value from one plugin to another, or to a team outside the cluster, is a kubectl command run by the cluster admin; the runbooks in docs/ spell them out.

Development

just ci                     # fmt, vet, tests, charts
just run sextant plugin-x   # the binary against your kubeconfig
just image sextant v0.1.0   # podman build

Publishing is just publish <plugin> <digest> --create with a functl login; see docs/fieldlab-2026-11.md for the plan and docs/obstacles.md for what Fundament had to change for this to work.

Licence

EUPL-1.2, like Sextant.