Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add the ability to deploy a remotecfg block #779

Closed
petewall opened this issue Oct 8, 2024 · 2 comments · Fixed by #805
Closed

Add the ability to deploy a remotecfg block #779

petewall opened this issue Oct 8, 2024 · 2 comments · Fixed by #805
Milestone
2.0

Comments

@petewall
Copy link
Collaborator

petewall commented Oct 8, 2024

This would enable the alloy instances deployed by the chart to be interoperable with the fleet management work.
@petewall petewall added this to the 2.0 milestone Oct 8, 2024
@petewall
Copy link
Collaborator Author

petewall commented Oct 8, 2024

There can only be one remotecfg, so add something like this inside each alloy instance block:

  remoteConfig:
    url: ""
    auth:
      type: "basic"
      username: ""
      password: ""
    id: <cluster-name>-<namespace>-<pod-name>
    pollFreq: 60s
    attributes:
      platform: kubernetes
      workloadType: statefulset

@petewall
Copy link
Collaborator Author

petewall commented Oct 8, 2024

https://grafana.com/docs/alloy/next/reference/config-blocks/remotecfg/

@petewall petewall linked a pull request Oct 16, 2024 that will close this issue
Add the ability to get config remotely #805
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0
Development

Successfully merging a pull request may close this issue.

Add the ability to get config remotely grafana/k8s-monitoring-helm
1 participant
@petewall