Bug 1461945 - [rfe] need nodeport docs
Summary: [rfe] need nodeport docs
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-15 16:51 UTC by Michael Burke
Modified: 2019-08-10 06:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-10 06:45:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Burke 2017-06-15 16:51:19 UTC
This issue is to address an outstanding GitHub issue: 
https://github.com/openshift/openshift-docs/issues/884#issuecomment-308764253

3.2
https://docs.openshift.com/enterprise/3.2/architecture/core_concepts/pods_and_services.html#service-nodeport

In 3.5: https://docs.openshift.com/container-platform/3.5/architecture/core_concepts/pods_and_services.html#service-nodeport


Who can request a nodeport on a service?
It mentions that "Setting a nodePort is a privileged operation." but doesn't specify what type of privilege. Is this an SCC-type privilege? Is this a cluster-admin privilege? It's unclear.

What happens if someone requests a port for a service that is already requested/in-use?

And so on and so forth.

This is related, in a larger sense, to the whole service guide. The guide does a good job of explaining the levers to pull and what they do, but we are missing a "bigger picture" description of when to use which and what and why, and what the drawbacks are to things.


Note You need to log in before you can comment on or make changes to this bug.