Bug 1461945 - [rfe] need nodeport docs
[rfe] need nodeport docs
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.5.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-15 12:51 EDT by Michael Burke
Modified: 2017-07-11 09:50 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Burke 2017-06-15 12:51:19 EDT
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.