Bug 1628615 - Document router behavior changes due to rhbz#1584701
Summary: Document router behavior changes due to rhbz#1584701
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Michael Burke
QA Contact: zhaozhanqi
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-13 14:51 UTC by François Cami
Modified: 2023-09-15 00:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 17:40:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description François Cami 2018-09-13 14:51:09 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.10/architecture/networking/routes.html#architecture-core-concepts-routes

Section Number and Name: 
"Alternate Backends and Weights"

Describe the issue: 
The change of behavior associated with https://bugzilla.redhat.com/show_bug.cgi?id=1584701 is not documented

Suggestions for improvement: 
"Setting `oc set route-backend` to 0 means the server will not participate in load-balancing but will still accept persistent connections."

Additional information: 
All credits to Michael Burke.

Comment 2 François Cami 2018-09-13 15:08:32 UTC
The change will be in 3.11 and will not be backported.

Comment 3 Michael Burke 2018-09-13 15:43:54 UTC
https://github.com/openshift/openshift-docs/pull/12025

Francois, PTAL

Comment 4 Michael Burke 2018-09-13 15:44:10 UTC
https://github.com/openshift/openshift-docs/pull/12025

Francois, PTAL

Comment 5 François Cami 2018-09-13 21:15:28 UTC
Github review done. Ben?

Comment 6 zhaozhanqi 2018-09-20 06:37:21 UTC
The changes LGTM.

Comment 8 Red Hat Bugzilla 2023-09-15 00:12:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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