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

masters are exposed on floatingip #348

Open
ioggstream opened this issue May 11, 2017 · 1 comment
Open

masters are exposed on floatingip #348

ioggstream opened this issue May 11, 2017 · 1 comment

Comments

@ioggstream
Copy link
Contributor

ioggstream commented May 11, 2017

I expect

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.

@ioggstream
Copy link
Contributor Author

@markllama @tomassedovic exposing masters and infra gives access to port 10250 too.

Is that fine?

Thx++,
R.

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

No branches or pull requests

1 participant