Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix sni sample fetch on ssl decyphered tcp conns #884

Merged
merged 2 commits into from
Jan 18, 2022

Conversation

jcmoraisjr
Copy link
Owner

Annotation based TCP Services has the ability to choose a TCP backend based on the TLS SNI extension sent by the client. HAProxy however has two distinct samples fetches for read the SNI extension, one used in pure TCP connections and the help of the inspect-delay, another one used on requests decyphered by haproxy. This distinction wasn't being made by the controller.

Should be merged to v0.13.

Annotation based TCP Services has the ability to choose a TCP backend
based on the TLS SNI extension sent by the client. HAProxy however has
two distinct samples fetches for read the SNI extension, one used in
pure TCP connections and the help of the inspect-delay, another one used
on requests decyphered by haproxy. This distinction wasn't being made by
the controller.

Should be merged to v0.13.
This is a cosmectic change: ingress updater is the responsible to
reflect the backend mode based on how the frontend was configured, this
is just replicating the behavior to the final configuration seems ...
correct.
@jcmoraisjr jcmoraisjr merged commit c401836 into master Jan 18, 2022
@jcmoraisjr jcmoraisjr deleted the jm-tcp-sni-sample branch January 18, 2022 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant