TheCodeAssassin

@ardigo I'm sometimes having problems with logspout not working anymore. My use case is the same as yours. I use the following DaemonSet: ``` apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name:...

@ardigo @josegonzalez my apologies. I opened a separate ticket: https://github.com/gliderlabs/logspout/issues/298

Maybe this PR would fix it? https://github.com/timescale/prometheus-postgresql-adapter/pull/47. Has this been released in the latest image on Dockerhub?

It would be great if it skips marking the schema as Optional when `Required` is set to `true`

+1

Hi @alexsomesan we already do this. The cluster is up and running and this is a separate repo from the clusters itself. It still doesn't work and still gives us...

@davidalger my apologies, I don't think I mentioned this but what I meant was that you cannot use different provider credentials in a module. Terraform then throws an error. Referring...

There is another issue here. For OIDC registrations flows, the return_to is not respected. When using the same OIDC flow for logins, everything works fine.

Hi @stevesloka , My secrets are stored as following: secret/environment/SECRET_VALUE the value is the actual secret value. I don't know if this format is unsupported for this tool. Some logs:...

We store strings but also certificates as base64. Maybe that could be causing problems? We store them as secret value=something. Every secret only has one value. We name them after...