Andreas Neubacher
Andreas Neubacher
No response yet. Note that the issue is intermittent for me. Failed repeatedly, then worked for a few days, then failed continuously again. Could not identify any pattern, yet.
@Gettokiwi : I can also confirm that this workaround solves the issue. Apparently the default "=0" setting for the port does not work in some environments. Could not clarify why...
Another scenario: I want to create certificates for cluster-internal S2S communication. My CA can generate certificates for "*._foo.bar_", but not for "cluster.local". Therefore, I'd like to change the cluster-internal domain...