Bug 1372338 - [DOCS] Enhancement for documentation regarding routing from Edge Load Balancers
Summary: [DOCS] Enhancement for documentation regarding routing from Edge Load Balancers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: brice
QA Contact: zhaozhanqi
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 12:56 UTC by Jaspreet Kaur
Modified: 2019-12-16 06:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 23:57:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jaspreet Kaur 2016-09-01 12:56:06 UTC
Document URL: https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#establishing-a-tunnel-using-a-ramp-node

Section Number and Name: 21.3. Establishing a Tunnel Using a Ramp Node 

7. Mark the ramp node as an unschedulable node so that no pods end up on the ramp node itself

Describe the issue: 	

What problem/issue/behavior are you having trouble with?  What do you expect to see?

The steps described for routing traffic from the edge load balancer servers (https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#establishing-a-tunnel-using-a-ramp-node) can be confusing.

Indeed when configuring the ramp node (https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#establishing-a-tunnel-using-a-ramp-node), the point 7 suggests marking the node as non-schedulable.

  Unfortunately, That action directly clashes with the next section for having an​ HA infra for ramp nodes (https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#configuring-a-highly-available-ramp-node).

The reason being that the ramp node once marked as non-schedulable is unable to receive the ipfailover pods which is required for HA Ramp node.

Suggestions for improvement: It should be made clear in documentation in which circumstances we need to make node unscheduled and scheduled 

Additional information:

Comment 1 brice 2016-09-13 06:11:37 UTC
PR submitted for this BZ, and verification given over IRC. Currently on peer review:

https://github.com/openshift/openshift-docs/pull/2830

Comment 2 openshift-github-bot 2016-09-16 04:28:54 UTC
Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/0ffe03f76728b0566c5bc32fd66392e0b899fea0
Merge pull request #2830 from bfallonf/unschedHA-1372338

Bug 1372338 edited step for making ramp node highly-available

Comment 4 brice 2016-09-28 05:44:24 UTC
My mistake, the released docs are not out just yet. Will be released at the next weekly release date.


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