FAQ: add entry about RHEL worker nodes

[miabbott]

A question came up in Slack about using the MCO with RHEL worker
nodes, so this tries to answer the question.

[runcom]

For reference, https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/2145/pull-ci-openshift-machine-config-operator-master-e2e-aws-workers-rhel7/1319673392265170944/artifacts/e2e-aws-workers-rhel7/gather-extra/pods/openshift-machine-config-operator_machine-config-daemon-2z4cl_machine-config-daemon.log <- rhel workers have an instance of the MCD running

👍

/approve

[yuqi-zhang]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: miabbott, runcom, yuqi-zhang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [runcom,yuqi-zhang]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sinnykumari]

Since this is a doc update, ci shouldn't be affected by the change.
/skip

[sinnykumari]

/retest

[sinnykumari]

/override ci/prow/e2e-agnostic-upgrade

[openshift-ci-robot]

@sinnykumari: Overrode contexts on behalf of sinnykumari: ci/prow/e2e-agnostic-upgrade

In response to this:

/override ci/prow/e2e-agnostic-upgrade

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.