Bug 1372338

Summary:	[DOCS] Enhancement for documentation regarding routing from Edge Load Balancers
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Documentation	Assignee:	brice <bfallonf>
Status:	CLOSED CURRENTRELEASE	QA Contact:	zhaozhanqi <zzhao>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	medium
Version:	3.2.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-27 23:57:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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 3 brice 2016-09-28 03:20:08 UTC

Link to released docs:

https://docs.openshift.com/container-platform/3.3/install_config/routing_from_edge_lb.html#establishing-a-tunnel-using-a-ramp-node

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.