Michal Veselý

I second removing the includes from all classes and instead going the way puppetlabs-apache went, as @ffrank suggested. We just upgraded to the newest version of collectd and going through...

Hello, can confirm that this problem is present on a different configuration too. Puppet: 5.3.2 Ruby: 2.0.0 Distribution: Ubuntu 14.04.5 LTS Module version: 2.0.1-rc0 This use-case worked on Puppet 3...

We are also affected by this issue for pods as soon as they start logging over 1k messages per second. As soon as the load calms down, log messages are...

Hello @fpetkovski, thanks for looking into this and sorry for the late reply. I am only seeing one instance of the operator across the entire cluster ``` miksercz@miksercz:~ $ k...

You must be right, since during the issue occurring we are seeing the "updating current Prometheus statefulset" message constantly with debug logging enabled. However, I am having a hard time...

Thanks for the explanation. I removed the above-mentioned hack to compare the resource differences and the issue disappeared again. I will prepare a verbose-logging image of the operator for when...

Hello everyone, the issue reoccurred again, this time thanks to @fpetkovski I tried watching for the specific resources during the incident and when checking out config maps in the relevant...

Hello, > Do you have something modifying prometheus rules in your system? I have not managed to think of anything, but our CI/CD system works by essentially running `kubectl apply`...