ungleich-user/deploy/k8s/dev
Sajeyks 24fe2122b4 Match the production LDAP layout from ungleich's sample entries
Sample entries from production show:
- customers live in ou=customer (singular), not ou=customers
- customers have gidNumber 10004 and staff 10002; uidNumbers are in
  the 10000s
- staff entries list organizationalPerson and person explicitly
- the servers serve ldaps:// on port 636

The app reads all of these from settings, so its behaviour is
unchanged; the customer entry it creates already matches production
attribute for attribute. The defaults and test setups were wrong:
env.sample, the Kubernetes ConfigMap (now ldaps:// without StartTLS,
gid 10004, start uid 10000), dev/env.dev and the dev LDAP seed now
mirror production. The made-up ou=groups is gone. The tests take the
customer DN and gidNumber from settings instead of hardcoding them.
2026-11-11 20:52:49 +03:00
..
e2e.sh Add a kind dev overlay with an end-to-end check 2026-11-06 15:53:58 +03:00
kustomization.yaml Match the production LDAP layout from ungleich's sample entries 2026-11-11 20:52:49 +03:00
ldap.yaml Add a kind dev overlay with an end-to-end check 2026-11-06 15:53:58 +03:00
mailpit.yaml Add a kind dev overlay with an end-to-end check 2026-11-06 15:53:58 +03:00
namespace.yaml Add a kind dev overlay with an end-to-end check 2026-11-06 15:53:58 +03:00
postgres.yaml Add a kind dev overlay with an end-to-end check 2026-11-06 15:53:58 +03:00