feat(kubeaid-security-exporter): add chart, move posture collection o… - #208
Merged
Conversation
…ff the agent Security posture collection becomes its own workload. The new chart owns the Deployment, Service, ServiceMonitor, the cluster-read ClusterRole and the ImageOutdatedAndVulnerable alert. kubeaid-agent drops all of it and now holds no CRD access whatsoever: the four Trivy report kinds, cilium.io, security.kubearmor.com, operator.kubearmor.com and networking.k8s.io/networkpolicies all move to a ServiceAccount that does nothing else. The services grant narrows to get, since the list verb was version-checker discovery and moved with the collector. The agent reaches the data over HTTP instead: securityPosture.interval is replaced by exporterURL and pollInterval. Polling is hourly rather than 12-hourly because the exporter serves a cached snapshot and the submit is skipped when collectedAt has not advanced, so freshness is bounded by the exporter collection interval rather than the agent poll. The alert moved with the metric it reads, now security_exporter_upgradable_vulnerable_images.
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
1 participant
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.
…ff the agent
Security posture collection becomes its own workload. The new chart owns the Deployment, Service, ServiceMonitor, the cluster-read ClusterRole and the ImageOutdatedAndVulnerable alert.
kubeaid-agent drops all of it and now holds no CRD access whatsoever: the four Trivy report kinds, cilium.io, security.kubearmor.com, operator.kubearmor.com and networking.k8s.io/networkpolicies all move to a ServiceAccount that does nothing else. The services grant narrows to get, since the list verb was version-checker discovery and moved with the collector.
The agent reaches the data over HTTP instead: securityPosture.interval is replaced by exporterURL and pollInterval. Polling is hourly rather than 12-hourly because the exporter serves a cached snapshot and the submit is skipped when collectedAt has not advanced, so freshness is bounded by the exporter collection interval rather than the agent poll.
The alert moved with the metric it reads, now security_exporter_upgradable_vulnerable_images.