Repository navigation
chore(infrastructure): remove dead Testkube manifests - #2013
Merged
Merged
Conversation
The testkube controller tree (HelmRelease, 14 vendored CRDs, namespace, networkpolicy) is referenced by no kustomization: it is absent from the base controllers aggregate and from both provider overlays, so it deploys nowhere. It still cost maintenance — Renovate kept bumping its chart (#1875) and every ksail validate run checked its ~50k lines of CRDs. Also drops the stale `testkube` namespace exemption from validate-replica-floor (the namespace no longer exists in any overlay). Validation: ksail workload validate green (301 files); prod validate's only failure is the pre-existing datreeio coroot_v1 schema gap (upstream CRDs-catalog #896), unrelated; kubectl kustomize builds green for both clusters. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![botantler-1[bot]](https://avatars.githubusercontent.com/in/1025824?s=60&v=4){kind=small}
devantler
added a commit
that referenced
this pull request
Jun 11, 2026
…mponent) The FQDN sweep originally pinned the testkube policy's world:443 egress, but main removed the entire dead testkube component, so the policy file goes with it — 12 pinned policies remain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
🎉 This PR is included in version 1.50.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
2 tasks
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the orphaned
k8s/bases/infrastructure/controllers/testkube/tree (HelmRelease, HelmRepository, namespace, networkpolicy, and 14 vendored CRD files — ~27k lines) and the staletestkubenamespace exemption invalidate-replica-floor.yaml.Why
This came out of a cost/efficiency sweep of the platform. Testkube is referenced by no kustomization: it is absent from the base controllers aggregate (
k8s/bases/infrastructure/controllers/kustomization.yaml) and from both provider overlays, so it deploys to neither cluster. It was pure dead weight that still cost maintenance:ksail workload validaterun schema-checked its ~50k lines of vendored CRDs.The only reference outside its own directory was the
testkubenamespace exemption in the replica-floor policy, removed here too (the namespace no longer exists in any overlay).Validation
ksail workload validate— ✅ 301 files validatedksail --config ksail.prod.yaml workload validate— 88 kustomizations validated, 1 pre-existing failure: the datreeiocoroot_v1schema gap (notificationIntegrationsnot in the upstream CRDs-catalog yet — fixed upstream in Update coroot.com/coroot_v1 schema from coroot-operator 0.9.7 datreeio/CRDs-catalog#896, unrelated to this change)kubectl kustomize k8s/clusters/local/— ✅ buildskubectl kustomize k8s/clusters/prod/— ✅ builds🤖 Generated with Claude Code