Context

As an ACM admin I want a logging turn key solution for my ACM fleet. We know from the MultiCluster Team that such a solution is not easy and requires careful architecture to reach a design that's maintainable & scalable. This requires multiple design iterations, that will only evolve if we experiment with ideas. This issue is suppose to build the ground work that will foster future design discussions.

In this PoC we will have the following assumptions :

• The store lives on the hub.
• 1 to 1 mapping between tenants and managed clusters
• No support for fine grained authZ
• No support the placements API
• No support for central Observatorium API

Goal

Provide an PoC on what a managed logging solution for forwarding & storing logs.

Acceptance criteria

• The ACM admin can enable this turn key solution somewhere in the capabilities field.
• Each managed cluster corresponds to a tenant on the store.
• As new managed clusters are added the forwarding & storage config are updated to accommodate for the new tenant
• The ACM admin can continue to use MCOA like it was initially designed and create Forwarders to Forward signals to other stores