Erwan Vallienne
Erwan Vallienne
Hello @sakeebshaikh74, This issue should be fixed by #25175. Before, Thanos query url configured in query-frontend was always using HTTP, regardless of ```https.enabled``` flag, causing the issue.
Hi @mmetc The readme is updated through a Github action on merge, no? Or has it changed? I can add them manually otherwise
/kind bug /area configuration
I'm not sure I understand why this condition exists, but it looks like the init containers register the agent only if ```tls.enabled``` or ```tls.agent.tlsClientAuth``` is true (not AND, but OR,...
> For now, why not set `tls.agent.tlsClientAuth` to `true` to use TLS authentication if you've already set `tls.enabled` to `true` ? I only use TLS to cipher cluster internal traffic....
Hello, I also encountered this issue today, and found a way to fix it by manually updating the tfstate (not ideal obviously). By checking the imported resource in the state...