Paweł Krupa

A lot of alerting rules here are taken from monitoring mixin projects (which produce "real" rule files). For more, you can see for example following sub-projects: - https://github.com/prometheus/prometheus/tree/master/documentation/prometheus-mixin - https://github.com/kubernetes-monitoring/kubernetes-mixin...

> Are you suggesting that it would be a good idea or bad idea to also produce some immediately useable templates? Mixins are written in [jsonnet language](https://jsonnet.org/), which allows overriding...

> Effects This is what alert name should be about as this is the first thing operator sees when receives alert. Additionally, this could be enhanced by `summary` annotation field....

I don't think there is any way of doing that without modifying a role. But we are happy to help with a PR which would allow such option :)

Thanks for reporting this. Could you create a PR with a fix? It should be as simple as editing one line I. `defaults/main.yml` file.

I wrote a shell wrapper to integrate github-changelog-generator, semver and chandler and I'm gonna leave it here: https://github.com/cloudalchemy/ansible-prometheus/blob/e9c766c6f68f40cbfb1743631aefcb39eb8a8079/.travis/releaser.sh

/refresh

@mkmik I think the most flexible would be to extend SealedSecrets CRD by adding the following: ``` spec: delimeters: right: "" left: "" ``` or ``` spec: template: delimeters: right:...

Also this matrix should be reflected by tests running in CI. Basically if we don't test it, it's not supported.

We've moved the helm chart to the other repository and simplified the Secret update procedure while changing it in tobs. Now it is easier (it is the same what you...