-
Notifications
You must be signed in to change notification settings - Fork 4.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
remove --cluster-cidr from kube-router's manifest. #3263
remove --cluster-cidr from kube-router's manifest. #3263
Conversation
Hi @murali-reddy. 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 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. I understand the commands that are listed here. |
Seems to be some issue running CI. I am investigating the failure. |
Can some one please help me why the CI is failing and where should i look for fixing it. I just removed |
@murali-reddy can you rebase? I fixed the problem on head, and #3183 will prevent it happening again. |
/ok-to-test |
/lgtm |
Kube-router was using --cluster-cidr flag to get the subnet allocated for pod CIDR's. But now kube-router has the ability internally to infer the CIDR allocated for the pod's by getting the information from kubernetes API server node spec's
3fc6a47
to
9b8f74d
Compare
/lgtm cancel //PR changed after LGTM, removing LGTM. @justinsb @murali-reddy |
@justinsb thanks. Have rebased. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, murali-reddy The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest ... flakey flakey |
/retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest At least it is flaking more consistently now :-) |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Kube-router was using --cluster-cidr flag to get the subnet allocated
for pod CIDR's. But now kube-router has the ability internally to infer
the CIDR allocated for the pod's by getting the information from
kubernetes API server node spec's