Skip to content

API changes to enable TCP keepalive configuration.#718

Merged
istio-testing merged 3 commits intoistio:release-1.1from
shakti-das:shakti/tcp-keepalive-r1.1
Nov 25, 2018
Merged

API changes to enable TCP keepalive configuration.#718
istio-testing merged 3 commits intoistio:release-1.1from
shakti-das:shakti/tcp-keepalive-r1.1

Conversation

@shakti-das
Copy link
Copy Markdown
Member

API changes PR for istio/istio#9378 for release 1.1

Signed-off-by: Shakti shaktiprakash.das@salesforce.com

Signed-off-by: Shakti <shaktiprakash.das@salesforce.com>
@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Nov 21, 2018
@istio-testing
Copy link
Copy Markdown
Collaborator

Hi @shakti-das. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@shakti-das
Copy link
Copy Markdown
Member Author

Comments from previous PR for master:

to release-1.1 branch
The issue asks for Mesh level configuration while what you are doing here is at DestinationRule level
Granted that you can define a Global DestinationRule, but it will get overwritten when someone declares something local. Does it make sense to move this to mesh/config.proto (its a bit of a kitchen sink right now). I don't mind having this in the DestinationRule (in fact we should have it there in addition to mesh config I guess).

This PR adds tcp_keepalive settings in DestinationRule and MeshConfig. The assignment logic would be as follows:
DestinationRule (if set, else next) > MeshConfig (if set, else next) > OS default (skip the envoy config)

Skipped keepalive probes and only kept keepalive time and interval for now. OS default probes will be sent.

@shakti-das
Copy link
Copy Markdown
Member Author

shakti-das commented Nov 21, 2018

@hzxuzhonghu pointed out in the other thread that probes is also part of requirement. So, adding probes as per istio/istio#9378 (comment).

I was thinking with these 3 items added, the message is similar to the one used in envoy proto. Does istio ever use imported protos from envoy? Code search doesn't show any prior art where envoy messages are reused in istio though, maybe to avoid dependency issues?

Signed-off-by: Shakti <shaktiprakash.das@salesforce.com>
Signed-off-by: Shakti <shaktiprakash.das@salesforce.com>
@shakti-das
Copy link
Copy Markdown
Member Author

@rshriram The review comments from PR #715 are implemented here. Please review.

Copy link
Copy Markdown
Member

@rshriram rshriram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@istio-testing
Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rshriram, shakti-das

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rshriram
Copy link
Copy Markdown
Member

/ok-to-test

@istio-testing istio-testing added ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member. and removed needs-ok-to-test labels Nov 25, 2018
@istio-testing istio-testing merged commit fd49366 into istio:release-1.1 Nov 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. ok-to-test Set this label allow normal testing to take place for a PR not submitted by an Istio org member.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants