Transfer retained Eve metadata ownership to Binjovi #59
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/binjovi-eve-metadata-ownership"
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?
Remove only Eve’s KratosIdentity CR after v0.1.35 delivered Retain and the exact Binjovi legacy-read and admin-network grants. Argo can prune the CR while the existing remote identity and password remain. The other four identity CRs and all credential resources stay in place.
Binjovi #778 binds Eve’s existing UUID and supports name, groups, and active-state management. It verifies CR absence before adoption and each metadata write. Keep the exact read and ingress grants for that check. Document that password Secret changes no longer rotate Eve’s password after this handoff.
Validation: source-retirement guard failed while Eve’s CR was present, then all tests/check.sh checks passed after source removal. Live v0.1.35 Retain CR is Ready at UID 9b879305-0775-4247-b26d-d3b63663a700. Existing remote UUID 04f900f9-7378-4f73-8a5b-78e8f7f1d649 and original password were independently verified. Release follows Binjovi #778 deployment.