feat(main): add e2e with kamaji case

[Andrey Kolkov (androndo)]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5286590c-c28a-4a51-988d-369d6a1211f8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Timofei Larkin (lllamnyp)]

Everything raised earlier is resolved.

• Rebased onto v1 cleanly (merge-base is v1's tip), so the stale fork point is gone.
• Plugin TLS tests reconciled to the corrected --cert-file detection — helpers_test.go now covers server-TLS-only, mTLS, no-cert-file, and mount-not-found via findSecretNameForTLS, with no overlap or helper-name collision against the getTLSConfig tests already on v1. Compiles and passes together.
• Seed IsVoter fix (Status().Update → Status().Patch(MergeFrom)) rebased cleanly and keeps its concurrent-writer regression test.
• Workflow-trigger changes dropped. I pushed a commit on top (f8bbeec, maintainer edit) reverting the master→main edits to ci.yml and publish.yml back to their v1 state — they're pre-existing workflows unrelated to adding e2e, and publish.yml in particular would have armed a push to a Docker Hub repo the project no longer owns. The new e2e.yml is untouched and still gates PRs.

Build, go vet, the full unit suite, and make manifests generate (no drift) all pass on the rebased tree.

The e2e suite itself is the strong part: it proves the full consumer story end to end — an operator-managed full-mTLS EtcdCluster backs a Kamaji DataStore, a TenantControlPlane comes up on it, and a ConfigMap written through the tenant API is then found as a key in our etcd. The harness dumps diagnostics from the EXIT trap before teardown, pins component versions with rationale, and is build-tag-gated so it stays out of unit runs.

LGTM.