You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our certificates for the system-internal-tls feature, we are still using certificates.LegacyFakeDnsName for legacy reasons and to make trust work on ingress layers that do not support trusting multiple SANs (like in contour and gateway-api).
As soon as this is resolved, we need to clean that up and remove certificates.LegacyFakeDnsName
The text was updated successfully, but these errors were encountered:
ReToCode
changed the title
Drop LegacyFakeDnsName in SANs
Encryption Cleanup: drop LegacyFakeDnsName in SANs
Mar 8, 2024
Description
In our certificates for the system-internal-tls feature, we are still using
certificates.LegacyFakeDnsName
for legacy reasons and to make trust work on ingress layers that do not support trusting multiple SANs (like in contour and gateway-api).As soon as this is resolved, we need to clean that up and remove
certificates.LegacyFakeDnsName
The text was updated successfully, but these errors were encountered: