feat(collectionagent): add the kubernetes kustomize casting - #176
Open
Nageshbansal wants to merge 11 commits into
Open
feat(collectionagent): add the kubernetes kustomize casting#176Nageshbansal wants to merge 11 commits into
Nageshbansal wants to merge 11 commits into
Conversation
Nageshbansal
force-pushed
the
feat/ca/k8s
branch
from
August 14, 2026 13:02
4a35920 to
2f9c6b9
Compare
Nageshbansal
force-pushed
the
feat/ca/k8s
branch
from
August 31, 2026 10:44
3fad548 to
5896622
Compare
Nageshbansal
changed the base branch from
feat/runner
to
fix/casting/kustomize-runner
August 31, 2026 11:07
Nageshbansal
force-pushed
the
feat/ca/k8s
branch
from
August 31, 2026 11:08
230aff3 to
028e761
Compare
Nageshbansal
force-pushed
the
fix/casting/kustomize-runner
branch
from
September 1, 2026 09:21
d3bd531 to
8453bd1
Compare
Nageshbansal
force-pushed
the
feat/ca/k8s
branch
from
September 1, 2026 09:21
028e761 to
78e705c
Compare
The pour follows the installation layout: a root kustomization and the namespace, with each collector kind's manifests, workload and config together in collector/<kind>/ behind a kustomization of their own. The workload manifest is written as workload.yaml, so a kind named for a workload (deployment) does not collide with its own config file. Per-kind templates replace the kind conditionals in the shared manifests, and the casting derives every pour path from ConfigKey rather than spelling the directory again.
The kubernetes kustomize casting poured a shared root that enumerated the collector kind's directory. A casting file holding two collection agents poured both documents over that one root, so the last document won it and cast applied its tree twice, never the other's. Every kind now pours a self-contained root under its own directory: the namespace and the kustomization move in beside the config the configMapGenerator reads, and cast applies the kind's root. The two per-kind kustomization templates collapse into the shared one, which names the generator and its file from the kind it renders against.
Nageshbansal
force-pushed
the
fix/casting/kustomize-runner
branch
from
September 3, 2026 14:27
8453bd1 to
ae04845
Compare
Nageshbansal
force-pushed
the
feat/ca/k8s
branch
from
September 3, 2026 14:27
78e705c to
2075ffc
Compare
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.
Features
kubernetes/kustomizecollection agent casting with two collector kinds:agentruns a DaemonSet on every node,deploymentruns a cluster-scoped Deployment behind a service. The SigNoz Kubernetes views need both.docs/examples/collectionagent/kubernetes/kustomize, one directory per kind.Example
Both collectors in one casting file:
Each kind pours its own root under
pours/collectionagent/collector/<kind>/, and either kind can be declared on its own.Related: https://github.com/SigNoz/platform-pod/issues/2754