-
Notifications
You must be signed in to change notification settings - Fork 38.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
Automated cherry pick of #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom #62854
Automated cherry pick of #62172: When using custom network with IP-alias, use the former's #62193: Fix IP-alias subnet creation logic #62398: Fix subnet cleanup logic when using IP-aliases with custom #62854
Conversation
This are fixes required to make (ip-alias + custom subnet) combination work for clusters. /cc @wojtek-t |
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process Pull Request Labels
|
/lgtm |
/retest |
cc @krzyzacy |
:/ |
I solved the problem by adding support for custom-network (which wasn't there earlier on 1.8 and hence SUBNETWORK and CREATE_CUSTOM_NETWORK variables were undefined). There is still this problem of using 'IP_ALIAS_SUBNETWORK' (that Jeff pointed out above), but we should never use it given that SUBNETWORK should always be set when CREATE_CUSTOM_NETWORK=true. I can fix that and create cherrypicks on other releases but IMO it isn't worth it (unless someone disagrees). |
cluster/gce/config-default.sh
Outdated
# If we're using custom network, use the subnet we already create for it as the one for ip-alias. | ||
# Note that this means SUBNETWORK would override KUBE_GCE_IP_ALIAS_SUBNETWORK in case of custom network. | ||
if [[ "${CREATE_CUSTOM_NETWORK}" == true ]]; then | ||
IP_ALIAS_SUBNETWORK="${SUBNETWORK:-IP_ALIAS_SUBNETWORK}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not fixed here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct... I explained why I left that unfixed in #62854 (comment)
I can do that if and cherrypick elsewhere if you think it;s worth it.
cluster/gce/config-test.sh
Outdated
# If we're using custom network, use the subnet we already create for it as the one for ip-alias. | ||
# Note that this means SUBNETWORK would override KUBE_GCE_IP_ALIAS_SUBNETWORK in case of custom network. | ||
if [[ "${CREATE_CUSTOM_NETWORK}" == true ]]; then | ||
IP_ALIAS_SUBNETWORK="${SUBNETWORK:-IP_ALIAS_SUBNETWORK}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not fixed here
Ok - thanks.
I disagree. We should fix that at head and cherrypick. But it can be separate PR + separate set of cherrypicks. /lgtm |
SGTM |
I created #63074 making that fix on HEAD and cherry-picked that commit into this PR (to save creating another one) |
bc7aa92
to
6a79494
Compare
kubemark is still failing... |
Hopefully it works now. |
e904842
to
69960aa
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shyamjvs, wojtek-t 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 |
And... kubemark is green. |
The other failures seem unrelated. |
/hold cancel |
/retest |
grrrr, DNS flakes again :( |
/lgtm |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #62172 #62193 #62398 on release-1.8.
#62172: When using custom network with IP-alias, use the former's
#62193: Fix IP-alias subnet creation logic
#62398: Fix subnet cleanup logic when using IP-aliases with custom