-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.13 Backports 2023-07-19 #26915
v1.13 Backports 2023-07-19 #26915
Conversation
[ upstream commit 04d48fe ] Use this workaround until the issue gets fixed: yaml/pyyaml#601 (comment) Signed-off-by: Michi Mutsuzaki <michi@isovalent.com> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
[ upstream commit 0bf7cc5 ] Only configure GetClientCertificate if client keypair is configured, allowing servers to Request ClientCertificates without requiring them. In docs for `GetClientCertificate` it specifies: > GetClientCertificate must return a non-nil Certificate. If > Certificate.Certificate is empty then no certificate will be sent to the > server. If a nil certificate is sent when the server requests a client certificate, the client will return an error. Instead, only configure GetClientCertificate if certificates are provided and the server may choose to how to handle the lack of a client certificate. This is needed primarily for when the server is using RequestClientCert, which requests a certificate, but does not require the client to send one. Previously, you would see this log message: ``` transport: authentication handshake failed: mTLS client certificate requested, but not provided ``` Now, if a server requires a client certificate it should reject the TLS connection and the client will receive the error from the server. Signed-off-by: Chance Zibolski <chance.zibolski@gmail.com> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
[ upstream commit 57249b1 ] Signed-off-by: toVersus <toversus2357@gmail.com> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
[ upstream commit b10d096 ] Otherwise, when the IPv6 is disabled, the check-log-errors fails with: Error while inserting service in LB map" error="Unable to upsert service [fd00:10:96::8f2f]:8080 as IPv6 is disabled" k8sNamespace=cilium-test k8sSvcName=echo-same-node Signed-off-by: Martynas Pumputis <m@lambda.lt> Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
/test-backport-1.13 Edit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
|
/test-1.26-net-next |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wonderful
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Once this PR is merged, you can update the PR labels via:
or with