[enterprise-4.10] Issue in file machine_management/creating-infrastructure-machinesets.adoc

[patrickstrick]

Which section(s) is the issue in?

Introduction of "Creating infrastructure machine sets"

What needs fixing?

I think that the first sentence could be clarified by using the wording from the OpenShift Sizing and Subscription Guide [1]. So instead of

You can use infrastructure machine sets to create machines that host only infrastructure components, such as the default router, the integrated container image registry, and the components for cluster metrics and monitoring.

...it would say (bold added to show difference in this change request)

To qualify as an infrastructure node and use the included entitlement, only components that are supporting the cluster, and not part of an end-user application, may be running on those instances.

The reason I believe this would be helpful is because I had a customer ask whether Service Mesh is allowed on the infrastructure nodes. The added point about "not part of the end-user application" explains why SM is not listed in the allowed applications, and might head off these questions in the future.

[1] https://www.redhat.com/en/resources/self-managed-openshift-sizing-subscription-guide

[JStickler]

@patrickstrick FYI https://issues.redhat.com/browse/OSSM-459

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.