-
Task
-
Resolution: Done
-
Major
-
Logging 6.0.0
-
2
-
False
-
None
-
False
-
NEW
-
OBSDA-550 - Updated APIs for Logging 6.0
-
NEW
-
When forwarding logs to CloudWatch using different AWS roles, all logs were incorrectly routed to the first AWS role defined. This change adds validation to reject when CloudWatch outputs are configured using multiple AWS roles.
-
Enhancement
-
-
-
Log Collection - Sprint 256, Log Collection - Sprint 257
Summary
As a user of Cloudwatch and ClusterLogForwarder,
my spec should be rejected if I define multiple CloudWatch Outputs with different web auth tokens
because the collector at this time only supports one web auth token config
Acceptance Criteria
- Verify spec with multiple CloudWatch outputs with different token auth is rejected
- Verify spec with multiple CloudWatch outputs with the same token auth is accepted
- Verify spec with multiple CloudWatch outputs with a mix of static and web auth tokens is accepted
- Verify AWS Container environment variables are only added once
Notes
- is related to
-
LOG-5539 When log forwarding to cloudWatch using different AWS Role, all logs arrives to the first
- Closed
- links to
-
RHBA-2024:137361 Logging for Red Hat OpenShift - 6.0.0
- mentioned on
(1 mentioned on)