-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 ipFamily validation #3483
Add ipFamily validation #3483
Conversation
Hi @tnqn. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, tnqn 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 |
/hold |
/hold cancel |
/test all |
@aojea @BenTheElder it seems specific role is needed to rerun the failed github actions, could you help rerun them? |
rebase and repush, I think that it triggers the github actions again |
Setting ipFamily to invalid value didn't return any error and kind just created an ipv4 cluster silently. It could be a bit confusing when it is set to some plausible but invalid values like IPv4, IPv6, Dual, ds. Signed-off-by: Quan Tian <[email protected]>
1b631bd
to
396586f
Compare
New changes are detected. LGTM label has been removed. |
/retest |
we can manually re-run, but I think actions only picks up config changes in the current branch I'm OK merging this without the actions passing since they're not really testing for this and the change isn't node-runtime specific, we can always manually bypass. |
Setting ipFamily to invalid value didn't return any error and kind just created an ipv4 cluster silently. It could be a bit confusing when it is set to some plausible but invalid values like IPv4, IPv6, Dual, ds.