-
Task
-
Resolution: Done
-
Blocker
-
Logging 5.4.0
-
3
-
False
-
None
-
False
-
OBSDA-108 - Distribute an alternate Vector Log Collector
-
VERIFIED
-
Logging (Core) - Sprint 220, Log Collection - Sprint 221
Summary
As a user of vector as a collector,
I want to be capable of configuring resources, tolerations, and nodeselctors like fluentd
so that I can tweak the deployment for my environment
Acceptance Criteria
- Verify vector is configured with resources from the ClusterLogging resource
- Verify vector is configured with tolerations from the ClusterLogging resource
- Verify vector is configured with node selector from the ClusterLogging resource
Notes
Impl:
collection: type: ["fluentd","vector"] fluentdSpec: {} vectorSpec:{} <= likely not needed for now resources: {} tolerations: {} nodeSelector:{} logs: {} <= deprecated
- spec honored for any collector
- logs.fluentd.[resource|tolerations|nodeSelector] take precedence over others for collector type fluentd
- logs.fluentdSpec are moved (e.g. webhook?)
- causes
-
OBSDOCS-488 spec.collection.logs has been deprecated in OpenShift Container Platform 4 - Cluster Logging 5.5 but still shows in examples
- Closed
- links to
- mentioned on