Bug 1696724 - Document procedure for moving openshift-console off control plane nodes
Summary: Document procedure for moving openshift-console off control plane nodes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
: 1696444 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 13:52 UTC by Derek Carr
Modified: 2021-06-29 12:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-12 11:56:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Derek Carr 2019-04-05 13:52:01 UTC
Description of problem:
Provide clear documentation for how to move the console to an alternate pool of nodes.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Derek Carr 2019-04-05 13:52:46 UTC
*** Bug 1696444 has been marked as a duplicate of this bug. ***

Comment 2 Samuel Padgett 2019-04-05 14:50:02 UTC
We currently only allow console to run on masters as a security measure because it handles user's tokens. This limits possible exposure since console is not running on the same node with user workloads. This is consistent with 3.x, which required console to run on masters.

Comment 3 Florin Peter 2019-04-07 18:26:23 UTC
Hi Samuel,

that is fine but as I can see there is no NodeSelector for the downloads deployment there is only a NodeSelector for console.

This is the output after I installed a cluster and added some infra nodes as you can see the downloads pods are not bind to the masters.

NAMESPACE                                               NAME                                                              READY   STATUS      RESTARTS   AGE    IP             NODE                                      NOMINATED NODE
openshift-console                                       console-b9c5857bc-5l4vs                                           1/1     Running     2          99m    192.168.0.36   ocp4-nmz4m-master-1                       <none>
openshift-console                                       console-b9c5857bc-rgzpl                                           1/1     Running     2          99m    192.168.4.28   ocp4-nmz4m-master-0                       <none>
openshift-console                                       downloads-6d44bf7f79-9gtb6                                        1/1     Running     0          69m    192.168.20.4   ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>
openshift-console                                       downloads-6d44bf7f79-scpk7                                        1/1     Running     0          99m    192.168.2.24   ocp4-nmz4m-master-2                       <none>

Comment 4 Kirsten Newcomer 2019-06-12 11:56:15 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.


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