HoloDeck 9.1.0.0 Deployment Fails During Authentik Initialization - PostgreSQL User Created but Database "authentik" Not Created

[jorgejcv]

Hello HoloDeck Team,

I am consistently encountering a deployment failure with HoloDeck 9.1.0.0 during the Authentik installation phase.

The issue has been reproduced multiple times using fresh HoloRouter deployments, always resulting in the same behavior.

Environment

• HoloDeck Version: 9.1.0.0
• Deployment Target: Existing vCenter Server
• Deployment Type: Single Site
• vSAN Mode: ESA
• Installation launched through:
  • Start-HoloDeckPrecheck
  • New-HoloDeckInstance
• All required binaries uploaded and validated (hash verification completed)
• Connectivity to vCenter successfully verified before deployment

Precheck Results

The deployment passes all HoloDeck prechecks successfully:

• HoloRouter services healthy
• Kubernetes operational
• GitLab operational
• DNS/DHCP deployment successful
• FRR/BGP deployment successful
• Vault deployment successful
• certsrv-proxy deployment successful
• TLS certificate issuance successful

The precheck ends with: 

[SUCCESS] Pre-Checks are complete

and deployment proceeds normally afterwards.

Deployment Progress

The deployment successfully completes the following stages:

Technitium DNS/DHCP

BGP Router (FRR)

Vault

certsrv-proxy

TLS certificate issuance

Deployment then reaches:

Installing Authentik

and waits for readiness:

Waiting for Authentik at

http://127.0.0.1:31080/-/health/ready/

The installer performs all 45 retries:

[RETRY 1/45]

...

[RETRY 45/45]

and eventually fails with:

[ERROR] Timed out waiting for Authentik after 450 seconds.

A screenshot of this stage is attached.

---

Investigation Findings

After the failure, we inspected the Kubernetes environment.

Pod Status

authentik-postgresql-0 Running

authentik-server-* Running (not Ready)

authentik-worker-* CrashLoopBackOff

PostgreSQL Logs

The PostgreSQL pod repeatedly reports:

FATAL: database "authentik" does not exist

PostgreSQL startup also shows:

PostgreSQL Database directory appears to contain a database; Skipping initialization

Authentik Server Logs

Repeated message:

PostgreSQL connection failed, retrying...

FATAL: database "authentik" does not exist

Authentik Worker Logs

Repeated message:

PostgreSQL connection failed, retrying...

FATAL: database "authentik" does not exist

PostgreSQL Investigation

From inside the PostgreSQL pod:

Environment variables:

POSTGRES_USER=authentik

POSTGRES_DB=authentik

POSTGRES_DATABASE=authentik

The user appears to be created correctly.

Query executed:

SELECT usename FROM pg_user ORDER BY usename;

Result:

authentik

However, querying databases:

SELECT datname FROM pg_database ORDER BY datname;

Result:

template1

Only template1 exists.

The expected database:

authentik

is not present.

Therefore PostgreSQL contains the Authentik user but does not contain the Authentik database.

Reproducibility

This has been reproduced multiple times with:

• Fresh HoloRouter deployment
• Fresh HoloDeck configuration
• Successful precheck
• Fresh deployment execution

Every attempt fails at exactly the same stage with the same PostgreSQL and Authentik errors.

Question

Is this a known issue in HoloDeck 9.1.0.0?

Can you advise why the PostgreSQL deployment creates the authentik user but does not create the required authentik database, resulting in Authentik startup failure?

Please let me know if additional logs or configuration files would be useful.

Thank you.