You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/clusteropenstack/configuration.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -153,6 +153,12 @@ openstack floating ip create <public network>
153
153
154
154
Note: Only user with admin role can create a floating IP with specific IP.
155
155
156
+
Note: When associating a floating IP to a cluster with more than 1 controller node, the floatingIP will be
157
+
associated to the first controller node and the other controller nodes have no floating IP assigned. When
158
+
the controller node has the floating IP status down CAPO will NOT auto assign the floating IP address
159
+
to any other controller node. So we recommend to only set one controller node when floating IP is needed,
160
+
or please consider using load balancer instead, see [issue #1265](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/1265) for further information.
161
+
156
162
### Disabling the API server floating IP
157
163
158
164
It is possible to provision a cluster without a floating IP for the API server by setting
0 commit comments