github-actions[bot]
commented
1 month ago This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
Request
Platform teams define infrastructure configuration, rbac and policy using GitOps systems such as Flux/Argocd with fleet repos while allowing individual teams (tenants) to define applications in team/tenant repos that map to kubernetes namespaces that are supported by Flux/Argo.
I would like to propose an option for defining Grafana Alloy configuration in Flux/Argo repos. We define multiple forms of infrastructure configuration within our Flux Fleet Repo and would like to see the same support given for Grafana Alloy.
Use case
Both Flux (Fluxcd) and Argocd support the ability to reconcile configuration in a git repository (such as github) with the configuration of kubernetes objects such as deployments, ingress, helm charts and more. This seems to be the same direction that Grafana Alloy is going, albeit with their own repo configuration. Can we get support for configuring Grafana Alloy using the same repo structures and reconcilation loops that already exist within these GitOps systems.