Update kube-router to v1.5.3

[chenliu1993]

Update kube-router to v1.5.3

Tried in aws provider using kops ans other components built based on master and it worked as it was in v1.2.3

[k8s-ci-robot]

Welcome @chenliu1993!

It looks like this is your first PR to kubernetes/kops 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kops has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @chenliu1993. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[hakman]

/ok-to-test

[chenliu1993]

/retest

[chenliu1993]

hi @hakman , I am trying to understand the process from promoting the kube-router version to stable channel and do a version-up. May I know what should be done to make sure the kube-router is ok to put in release? I notice that there is some tests trigger by pull lies in test-infra?

[hakman]

Thanks @chenliu1993.
It looks good now that pull-kops-e2e-cni-kuberouter is passing. Generally, there are other changes to the manifest, but there were no changes to any of the files in https://github.com/cloudnativelabs/kube-router/tree/master/daemonset for the last 3 years. Maybe once 2.0.0 will be out, there will be something more to change.
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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:

• OWNERS [hakman]

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

[chenliu1993]

Thanks @chenliu1993. It looks good now that pull-kops-e2e-cni-kuberouter is passing. Generally, there are other changes to the manifest, but there were no changes to any of the files in https://github.com/cloudnativelabs/kube-router/tree/master/daemonset for the last 3 years. Maybe once 2.0.0 will be out, there will be something more to change. /lgtm /approve

Thank you @hakman for the information!
And I also noticed that a issue is looking for kube-router manintainer, if no one is taking this and you are still finding, I'd like to help 😊