-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
security: Open ports 9000-9999 inside the cluster for host network services #683
security: Open ports 9000-9999 inside the cluster for host network services #683
Conversation
Change in OpenShift in 2017: openshift/openshift-ansible#5345 |
…rvices In OpenShift 3.x we opened 9000-9999 for TCP for all internal connections between masters, infra, and workers so that we could have a range that host level services inside the cluster could coordinate on. This range is analogous to node ports, except unlike node ports it is only available on the inside. The most common consumers are node network metrics ports (node exporter, cluster version operator, network operator, sdn, node proxy) that need to be reachable from prometheus without magic tricks. A second set is internal secured services that want to connect but must be host network, like gluster, storage services, or other cluster level proxies. Open the range 9000-9999 by default so that new services don't require either a reinstall or manual management. Future changes in the platform may autoallocate from this range, but for now teams must reserve.
dfd2cc8
to
3248996
Compare
images flake is openshift/release#2070. /retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Documented openshift/origin#21520 |
These were added in 3248996 (security: Open ports 9000-9999 inside the cluster for host network services, 2018-11-15, openshift#683) with a commit message that claimed the range should be through 9999. Catch the code up with that message.
In OpenShift 3.x we opened 9000-9999 for TCP for all internal connections
between masters, infra, and workers so that we could have a range that
host level services inside the cluster could coordinate on. This range
is analogous to node ports, except unlike node ports it is only available
on the inside. The most common consumers are node network metrics ports
(node exporter, cluster version operator, network operator, sdn, node
proxy) that need to be reachable from prometheus without magic tricks.
A second set is internal secured services that want to connect but must
be host network, like gluster, storage services, or other cluster level
proxies.
Open the range 9000-9999 by default so that new services don't require
either a reinstall or manual management. Future changes in the platform
may autoallocate from this range, but for now teams must reserve.
Consistent with 3.x, blocks CVO metrics from being read by prometheus-k8s.