We have recently upgraded our platform to Graylog 4.0 and while going through the steps of Upgrading from the Collector Sidecar we noticed that “the new Sidecars don’t assign configurations based on tags anymore. Instead you have to assign configurations explicitly”.
We were able to complete the upgrading without any issues, but given the quite dynamic characteristics of our sidecars we would like to handle the assignation similar as it was before, is there any way to do it?
We deploy our Graylog sidecars over kubernetes: we use a daemonset to deploy a sidecar pod in each of the nodes (16) we have in the cluster. If there are unnoticed issues with the pods, they die o stop sending logs, when eventualy they are back, we will see the sidecars running but the match with the configuration would be missing.
How could we deal with this situation? A ‘static’ name for the sidecars pods would keep the match alive even if the pod itself is not the same?
Many thanks for your comments.