-
Notifications
You must be signed in to change notification settings - Fork 261
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
not assign floating ip when there are multiple controller nodes #1276
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc 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 |
16e7586
to
8b5c5d3
Compare
@@ -153,6 +153,12 @@ openstack floating ip create <public network> | |||
|
|||
Note: Only user with admin role can create a floating IP with specific IP. | |||
|
|||
Note: When associate floating ip to a cluster with more than 1 controller nodes, the floating ip will be |
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.
Note: When associate floating ip to a cluster with more than 1 controller nodes, the floating ip will be | |
Note: When associating a floating IP to a cluster with more than 1 controller node, the floating IP will be |
@@ -153,6 +153,12 @@ openstack floating ip create <public network> | |||
|
|||
Note: Only user with admin role can create a floating IP with specific IP. | |||
|
|||
Note: When associate floating ip to a cluster with more than 1 controller nodes, the floating ip will be | |||
associated to the first controller node and the other controller nodes doesn't have floating ip. When |
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.
associated to the first controller node and the other controller nodes doesn't have floating ip. When | |
associated to the first controller node and the other controller nodes have no floating IP assigned. When |
00d20f1
to
297620f
Compare
// assign to portID, so it's already assigned and no need action | ||
// the other is fp.PortID assigned to another fixed ip (the other control plane) | ||
// so no actions for both situations | ||
if len(fp.PortID) != 0 { |
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.
What do you think about doing this check in the machine reconciler instead, because networking.Service#AssociateFloatingIP
is also called from other locations where we potentially want to reassign the FIP, even if it is already assigned to another port
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.
yes, updated ,thanks~
@apricote please help check whether current way is better.. thanks |
/lgtm The commit looks like a merge commit, might want to take a look at that. |
not sure what's a merge commit?? |
/lgtm |
/hold cancel |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1265
Special notes for your reviewer:
TODOs:
/hold