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
While this works, the UX of needing to create a secret that has no use just to create the TLSContext should be improved.
Note:
This is also relevant for verifying client certificates. While you would expect Ambassador to be terminating TLS if it is verifying client certificates, there could be a usecase where you just want client cert verification. TLS certificates must be provided for this usecase as well
The text was updated successfully, but these errors were encountered:
This mostly plays a role when creating a
TLSContext
for originating TLS to upstream services where tls certificates need not be provided.Currently, if I needed to enforce strict minimum tls version for origination to upstream service, I would expect to create a
TLSContext
like this:and use it in a
Mapping
like this:However, checking the logs, it looks like Ambassador rejects any
TLSContext
that does not provide certificatesso you are required to create a certificate just to create the
TLSContext
to enforce min tls version:While this works, the UX of needing to create a secret that has no use just to create the
TLSContext
should be improved.Note:
This is also relevant for verifying client certificates. While you would expect Ambassador to be terminating TLS if it is verifying client certificates, there could be a usecase where you just want client cert verification. TLS certificates must be provided for this usecase as well
The text was updated successfully, but these errors were encountered: