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've encountered an issue where, after changing the container service image tag from dev.com:v1.0.0 to dev.com:v2.0.0, the logs are still being sent to Elasticsearch with the image tag showing as dev.com:v1.0.0.
I attempted to resolve this by restarting Filebeat, which successfully sent the logs with the updated image tag dev.com:v2.0.0.
I'm using Filebeat v7.9.2 in the RKE cluster.
How can I handle this issue?
Thank you.
The text was updated successfully, but these errors were encountered:
Hey everyone,
I've encountered an issue where, after changing the container service image tag from dev.com:v1.0.0 to dev.com:v2.0.0, the logs are still being sent to Elasticsearch with the image tag showing as dev.com:v1.0.0.
I attempted to resolve this by restarting Filebeat, which successfully sent the logs with the updated image tag dev.com:v2.0.0.
I'm using Filebeat v7.9.2 in the RKE cluster.
How can I handle this issue?
Thank you.
The text was updated successfully, but these errors were encountered: