Document URL: https://docs.openshift.com/container-platform/4.0/machine_management/manually-scaling-machineset.html Section Number and Name: Scaling a MachineSet manually Describe the issue: ~~~ The default installation creates only one router. If you scale down your cluster, the node that hosts the router pod might be removed. In this case, you temporarily cannot access the web console and some other resources. After the router pod is redeployed to a different node, service will be restored. ~~~ Suggestions for improvement: It says that default router is 1 but the default router is 2. ~~~ $ oc get pod -n openshift-ingress NAME READY STATUS RESTARTS AGE router-default-6f585b86bc-gv2h8 1/1 Running 0 166m router-default-6f585b86bc-p6pcq 1/1 Running 0 166m $ oc get relicaset -n openshift-ingress NAME DESIRED CURRENT READY AGE replicaset.apps/router-default-6f585b86bc 2 2 2 166m ~~~ I deployed ocp4 with ./openshift-install-latest unreleased-master-490-g0ddac41932688237c599cc8a7231d624a08dfc29 which is the latest source of openshift installer as of today(2019/March/4) Additional information:
The PR's here: https://github.com/openshift/openshift-docs/pull/13982 If it's creating two routers, I think that we can remove the entire note. Hongan Li, will you PTAL?
please see my comments in the PR
Thank you! I've merged the change and am waiting for it to go live.
This change is live.https://bugzilla.redhat.com/show_bug.cgi?id=1685346#