Skip to content
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

Assign pre-existent IP to bastion - fixed_ips doesn't work #208

Closed
maniasso opened this issue May 25, 2021 · 3 comments · Fixed by #209
Closed

Assign pre-existent IP to bastion - fixed_ips doesn't work #208

maniasso opened this issue May 25, 2021 · 3 comments · Fixed by #209

Comments

@maniasso
Copy link

I've noticed that is only possible to assign the bastion_vip which is used for keepalived when 2 HA bastion servers are set.
the fixed_ips is ignored at bastion, only fixed_ip_v4 which is used by bastion_vip and keepalived is used, is possible to add the possibility to assign a pre-defined IP to bastions when use HA?

@yussufsh
Copy link
Contributor

@cs-zhang

@maniasso
Copy link
Author

An issue I see when assign pre-existent IPs to masters, bootstrap and workers, there's a risk to bastion gets the IP that should be reserverd to OCP cluster and builds stop since IP is already in use, so a good practice would be have the possibility to determine the IP the bastion(s) will have as well.

@cs-zhang
Copy link
Collaborator

That is caused by the static IP is not support the bastion HA, I'll add it. In this case, all VMs created by TF need to use static IP, or not use it at all.

bpradipt added a commit that referenced this issue Jul 1, 2021
Enable bastion HA support to use pre-defined IPs, fix #208
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants