g1franc
g1franc
I confirm the same behaviour: - with Dynatrace -> illegal instruction - without Dynatrace -> working as expected
> According to these release notes, this might be solved with the latest version of dynatrace: https://docs.dynatrace.com/docs/whats-new/release-notes/oneagent/sprint-285 > > Regardless, can probably close this issue as it's clearly a dynatrace...
Maybe one day, it will come to ease the life
I have the same issue and I plan to provide a PR to quickly address the issue
@longwuyuan I'm configuring proxy-ssl-protocol because the backend is using TLS (HTTPS) but I don't need to provide a secret for the TLS client certificate as the backend don't use one...
Hello @longwuyuan, Maybe I misunderstood your test, but it seems that you tested NGINX serving TLSv1.3 while the issue is about the Operator configuring NGINX to proxify to an TLSv1.3...
Could I suggest to introduce a new parameter as "string" ? Code would support both the legacy map[string]string and the new "simple" string for some time, with the map being...