coordinator: remove ownerreference from configmaps

[burgerdev]

The ConfigMaps used to store Coordiantor history are not owned by the Coordinator StatefulSet anymore. Cleaning them up now requires manual deletion, but the ConfigMaps can now be used by more than one Coordinator set and restored ConfigMaps are consistent with the ones created by the Coordinator.

Fixes CON-208.
Fixes CON-220.
Fixes CON-205.

[github-actions]

Do the documentation changes need to be backported?

Changes to /docs/docs won't be visible until the next release.
If you are fixing something in the docs that should be immediately visible, the changes needs to be made to both /docs/docs and /docs/versioned_docs/version-X.Y, where X.Y is the version of the latest minor release.
This can be done in this same PR.

• Yes, this should be backported to the current version of the docs.
• No, the PR only contains docs changes relevant for future versions.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-07-09 06:42 UTC

[linear-code]

CON-208

CON-220

CON-205

[burgerdev]

I discovered a regression while working on the multi-coordinator e2e test: the configmaps returned to the client were missing the TypeMeta. Fixed that and added a regression test.

• coordinator test

[charludo]

LGTM, thanks! I'll open a PR for govulncheck...