You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Promtail 2.1 with Loki 2.1 running in a single node microk8s cluster, installed via their respective Helm charts, and it seems Promtail gets momentarily confused when a pod is recreated, causing events from the new pod being erroneously labeled under the previous pod name, while also including the same events under the current pod name, resulting in duplication of the events.
In this scenario, I have a k8s deployment called "stagehand" and a pod stagehand-6d4ff786c-vx8jw which was deleted, and a new pod is automatically recreated as stagehand-6d4ff786c-zmn47. The log lines during startup of the new pod zmn47 are being duplicated.
Easiest just to demonstrate this with an annotated screenshot from Grafana:
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
A stale issue or PR that will automatically be closed.
label
Jun 3, 2021
the current dummy credentials deny using EKS IAM service accounts, removing this line fallback to the AWS SDK default which is the following:
* Environment Variables
* Shared Credentials file
* Shared Configuration file (if SharedConfig is enabled)
* EC2 Instance Metadata (credentials only)
@jtackaberry did you fix prombles by this merged? I face same prombles but in my case duplication log always exists by time while you just The duplication stops after a couple seconds
by the way, my k8s cluster has annotation "kuberntes.io/config.hash"
sorry if bother your time.
I have Promtail 2.1 with Loki 2.1 running in a single node microk8s cluster, installed via their respective Helm charts, and it seems Promtail gets momentarily confused when a pod is recreated, causing events from the new pod being erroneously labeled under the previous pod name, while also including the same events under the current pod name, resulting in duplication of the events.
In this scenario, I have a k8s deployment called "stagehand" and a pod
stagehand-6d4ff786c-vx8jw
which was deleted, and a new pod is automatically recreated asstagehand-6d4ff786c-zmn47
. The log lines during startup of the new podzmn47
are being duplicated.Easiest just to demonstrate this with an annotated screenshot from Grafana:
The duplication stops after a couple seconds.
Here's the relevant log excerpt from Promtail:
FWIW, I have Fluent Bit sending to Elasticsearch on the same node and there's no duplication there.
The text was updated successfully, but these errors were encountered: