EventHorizon Qdrant was converted from an unused ephemeral service into durable, authenticated backend infrastructure. No game data is embedded or indexed by this change.
v1.14.1 to v1.18.3.emptyDir with the 10 Gi event-horizon-qdrant PVC using local-path storage.QDRANT_API_KEY Gitea Actions and Kubernetes runtime secret./qdrant/storage on the PVC.Repository merge: f8d28f4256cc191aae0929b3cd6d470070c7a5b6.
The first rollout exposed that Qdrant v1.18.3 writes snapshots and its initialization marker beneath root-owned /qdrant by default. With UID 1000 enforcement this caused a temporary readiness outage. The committed manifest was corrected to place all runtime writes under the mounted PVC and was applied directly to restore service while CI converged on the same repository state.
1/1 ready.1/1 ready.Bound, 10 Gi, local-path.401./ and /readyz return HTTP 200; readiness reports Postgres and Qdrant ready.Revert the repository merge and deploy through the normal EventHorizon workflow. Do not delete the Qdrant PVC during rollback; retaining it preserves vector data for forward recovery. If reverting authentication, coordinate backend and Qdrant configuration in one rollout to avoid readiness failure.