Open PatMis16 opened 7 months ago
can you check if grafana/agent
image can be pulled into your cluster to be operational? Some pod logs would be helpful :D
Hi there :wave:
On April 9, 2024, Grafana Labs announced Grafana Alloy, the spirital successor to Grafana Agent and the final form of Grafana Agent flow mode. As a result, Grafana Agent has been deprecated and will only be receiving bug and security fixes until its end-of-life around November 1, 2025.
To make things easier for maintainers, we're in the process of migrating all issues tagged variant/flow to the Grafana Alloy repository to have a single home for tracking issues. This issue is likely something we'll want to address in both Grafana Alloy and Grafana Agent, so just because it's being moved doesn't mean we won't address the issue in Grafana Agent :)
Hi Guys,
Thanks for all the responses. Got it working now. For some reason I had to change the port to 12345.
What is the difference between the Grafana Agent and Grafana Alloy?
BR, Patrick
Thanks for all the responses. Got it working now. For some reason I had to change the port to 12345.
That's strange, it sounds like it might be a bug somewhere in the chart since the readinessProbe should be bound to the listenPort
setting on the Helm chart.
What is the difference between the Grafana Agent and Grafana Alloy?
Grafana Alloy is the evolution of flow mode, renamed in part to make a splash for the 1.0 release (Alloy was released as 1.0). There are minor differences to be aware of when migrating, but Grafana Alloy is Flow mode, with the same concepts, configuration, and components.
That's weird as indeed, the readiness probe reuses the listenPort.
Could it be related to this change last month for merging the agent and alloy keys, and it picking up some other default?
Checking with both keys present, the .Values.agent
listenPort takes precedence and I wouldn't expect to have any issues here.
Could it be related to this change last month for merging the agent and alloy keys, and it picking up some other default?
I don't think so, since the issue reported here was for the Agent Helm chart, not Alloy's.
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!
What's wrong?
Following deployment of the agent using a Helm chart to Kubernetes, the readinessProbe consistently fails with a "connection refused" error. We are only using our own container repository for this deployment, which acts as a proxy for the original container repository on Docker Hub.
Steps to reproduce
Use this deployment (original container repo):
System information
No response
Software version
Grafana Agent 0.40.3
Configuration
No response
Logs