Edvin N

Ahh just as I thought there was some flag to define some address. Thanks allot for the quick response @rikatz! I guess this possibility already exist when I don't run...

Sorry for the delay @rikatz, I have verified and setting `- --internal-logger-address=127.0.0.1:11515` solved the issue. I think I should have time some time later next week to create a PR...

@rikatz you wrote earlier "Also be aware that as soon as you are binding to hostNetwork this port will be exposed in your host and someone can push rogue messages...

Was planning to start to do a contribution in the helm chart but remembered that the extraArgs is already in place (I'm already using it). I will create a documentation...

@Iridias could you recreate this PR and use another branch then master? I was going to fix the CI but I can't since it's your master branch. Or you can...

We will continue this PR in https://github.com/grafana-operator/grafana-operator/pull/821

Would love to see this feature, there have also been talk about it on slack so I think other people would like it as well. I do think we first...

So i have read up on grafana rbac https://grafana.com/docs/grafana/latest/manage-users/ In short a user exist in grafana. That user can be a part of one or multiple organizations. In a organization...

Considering scope creep with supporting external Grafana instances https://github.com/grafana-operator/grafana-operator/issues/497 how interesting is this still? Do we think this still is a reasonable feature to add to the operator?

@cheddarwhizzy that sounds really interesting, if you manage to get it to work it would be really nice to have a blog post or something similar on how you solved...