-
Spike
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Logging - Sprint 280
Summary
Investigate ways that project administrators may spec and administer container log forwarding for their project workloads without exposing other namespaces to the the collector.
Acceptance Criteria
- Summarize findings in a comment
- Link any relevant resources or documents.
- Create an openshift/enhancement document for broader review
- Gain consensus of design and effort from the logging team and other stake holders
- Create an Epic and follow-up task for implementation efforts
Notes
- Primarily need to determine how to ensure the forwarder is not able to mount logs from other namespaces, allow users to exec into the container and see other namespace logs (i.e. by mounting /var/log/pods), etc
- informs
-
OBSDA-320 ClusterLogForwarder configuration by namespace admin so each project can configure their log sink according to their needs and requirements
-
- To Do
-