feat: prepare Eve identity retention and Binjovi access #57
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/kratos-eve-handoff"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Prepare Eve for metadata management by Binjovi. Set Retain on the existing KratosIdentity so later source removal preserves its remote UUID and credentials. Keep the identity resource present in this release.
Allow the Binjovi control-plane pods to reach Kratos admin TCP4434. Grant its ServiceAccount GET access only to the Eve KratosIdentity so it can prove the legacy owner is absent before adoption and writes. Identity creation, passwords, and other user resources remain with their current sources.
Validation: all Ory route and new handoff source contracts passed. API-server dry-run accepts the Retain CR, network policy, and exact Role/RoleBinding. The deployed Kratos operator v0.5.23 has already passed a live disposable identity Retain proof, including deletion after password Secret removal.