-
Spike
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
NEW
-
OBSDA-747 - [MCOA] Deliver CLO via ACM
-
NEW
-
Release Note Not Required
-
-
-
Log Storage - Sprint 239, Log Storage - Sprint 240, Log Storage - Sprint 241, Log Storage - Sprint 242
Background
The OpenShift Logging product team has been tasked to evaluate options on how to offer multi-cluster (infrastructure) logging based on existing components and Red Hat offerings. Part of this evaluation is to explore which options of integration and level of such are offered by the Red Hat Advanced Cluster Management (RHACM) product.
This exploration work consists of two separate options:
- Explore how to utilize the RHACM Policy Controller to declare and distribute ConfigurationPolicy resources across a fleet of clusters that resemble a multi-cluster infrastructure logging scenario. This has been addressed by openshift-logging/log-storage-toolbox#14
- Explore how to utilize the RHACM klusterlet-addon framework and APIs to distribution OpenShift Logging custom resources and configuration hat resemble a multi-cluster infrastructure logging scenario. This is the current task of this spike. (More info on the Add-on Developer Guide)
Goals
- Provide a proof-of-concept klusterlet-addon implementation for a multi-cluster OpenShift Logging rollout on a fleet of clusters.
- Limit the implementation on Vector and LokiStack only.
- Limit the implementation on mTLS based authentication between collectors on spoke clusters and Lokistack on the hub cluster.
Developer Notes
- TBD
- relates to
-
OBSDA-356 Multicluster Log Storage to Loki
- In Progress
- links to