Closed anders-elastisys closed 2 weeks ago
Hi @anders-elastisys. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
Thanks @anders-elastisys /approve
/release-note-edit
Add support to use existing fips with terraform OpenStack
@yankay @cyclinder Hi, I believe a reviewer needs to add a lgtm
label for this to be merged, could one of you help with this?
@yankay @cyclinder Hi, I believe a reviewer needs to add a
lgtm
label for this to be merged, could one of you help with this?
HI @tico88612 @VannTen Could you please help review it? Thanks!
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: anders-elastisys, tico88612, yankay
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What type of PR is this? /kind feature
What this PR does / why we need it:
This PR adds Terraform Openstack support for specifying existing floating IPs on each machine listed in
k8s_nodes
andk8s_masters
with a new optional variablereserved_floating_ip
which is only used when thefloating_ip
variable is set to true. Ifreserved_floating_ip
is not set andfloating_ip
is true, a new floating IP will be created same as before.When
reserved_floating_ip
is set, that IP will get released and not deleted when deleting all Terraform resources.Known limitations:
reserved_floating_ip
on multiple hosts, Terraform will not complain and only one machine gets assigned the IP in the end, as there is currently no check for whether or not the specific IP has already been assigned. The output will show the same IP several times as well.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: