-
Story
-
Resolution: Done
-
Critical
-
None
-
5
-
False
-
None
-
False
-
NEW
-
API, Deploy
-
NEW
-
-
Technology Preview
-
-
-
Log Collection - Sprint 244, Log Collection - Sprint 245, Log Collection - Sprint 246, Log Collection - Sprint 247, Log Collection - Sprint 248
Summary
As a user of only a receiver input,
I want to deploy the log collector as a deployment instead of daemonset
Because I do not require the collector to run on every node
Acceptance Criteria
- Verify audit logs are received via the receiver and forwarded to configured outputs
- Verify the pod no longer mounts the host file system
- Verify the collector is a deployment when only a receiver input is referenced in the pipelines
- Verify the collector is a daemonset when a receiver input and other built-in inputs (application, infrastructure, audit) are defined in pipelines
- Ensure feature is behind a feature-gate
Notes
- This addresses the HCP usecase that utilizes one collector per NS for collecting audit logs via a webhook
- Saves deployment resources
- Collector does not need to mount the host file system given it only receives logs via the receiver
- links to
- mentioned on