-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add implementation of SDS. #1935
Conversation
Signed-off-by: Kuat Yessenov <[email protected]>
update envoy
to include the SNI inspecting method, for using SNI in telemetry and policies Signed-off-by: Vadim Eisenberg <[email protected]>
…a38ad58121ba5aa5af51 Signed-off-by: Vadim Eisenberg <[email protected]>
…_3b05bffcbaedaf6d112ba38ad58121ba5aa5af51 update Envoy's SHA to latest, to implement SNI telemetry reports and policy checks
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
…equested_server_name_attribute Add connection requested server name attribute to TCP read filter
…equested_server_name_attribute Revert "Add connection requested server name attribute to TCP read filter"
Signed-off-by: Kuat Yessenov <[email protected]>
* add rbac filter to istio http integration test. * rename issueer for rbac test.
Apparently, automake is now installed automatically, which broke the brew install step. Signed-off-by: Piotr Sikora <[email protected]>
Signed-off-by: Piotr Sikora <[email protected]>
Before: $ bazel-bin/src/envoy/envoy --version bazel-bin/src/envoy/envoy version: 0/1.8.0-dev//DEBUG After: $ bazel-bin/src/envoy/envoy --version bazel-bin/src/envoy/envoy version: f315a32fc7c6f727fc9645cc1ca27d4160c1d0e0/1.8.0-dev/Clean/DEBUG Fixes #1803. Signed-off-by: Piotr Sikora <[email protected]>
Signed-off-by: Piotr Sikora <[email protected]>
Signed-off-by: Piotr Sikora <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Wayne Zhang <[email protected]>
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
/lgtm /approve |
@JimmyCYJ: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JimmyCYJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Release note: