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
there should be an option to avoid exposing masters.
From the doc:
Master nodes and infra nodes have floating IP assigned to make sure these nodes are accessible when an external loadbalancer is used for accessing OpenShift services.
So if we use a LBaaS, we should be able to avoid assigning floating ips to masters.
this could be done
with conditions, eg.
feedback welcome!
diff --git a/master.yaml b/master.yaml
index 2989e1d..cd7f9b7 100644
--- a/master.yaml
+++ b/master.yaml
@@ -1,4 +1,4 @@
-heat_template_version: 2014-10-16
+heat_template_version: newton
@@ -242,6 +242,10 @@ parameters:
+conditions:
+ expose_masters: false
+
+
resources:
@@ -319,6 +323,7 @@ resources:
# Provide access to the Master on the public network
floating_ip:
+ condition: expose_masters
type: OS::Neutron::FloatingIP
properties:
floating_network: {get_param: external_network}
Moreover we could limit ssh access to master and infra using remote_group_id in security groups.
The text was updated successfully, but these errors were encountered:
I expect
there should be an option to avoid exposing masters.
From the doc:
So if we use a LBaaS, we should be able to avoid assigning floating ips to masters.
this could be done
with conditions, eg.
feedback welcome!
Moreover we could limit ssh access to
master
andinfra
usingremote_group_id
in security groups.The text was updated successfully, but these errors were encountered: