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
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
ReToCode
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jun 7, 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: