openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS-66340: Removed Both OpenShift Logging and Red Hat OpenShift Service Mesh deploy Elasticsearch...

Browse Source
This commit is contained in:
dfitzmau
2025-12-03 15:00:12 +00:00
committed by openshift-cherrypick-robot
parent 6ebfb32805
commit 05cd312b3e
6 changed files with 1 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
nodes/nodes/nodes-nodes-creating-infrastructure-nodes.adoc
View File

@@ -11,8 +11,6 @@ include::snippets/machine-user-provisioned-limitations.adoc[leveloffset=+1]
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. These infrastructure machines are not counted toward the total number of subscriptions that are required to run the environment.
In a production deployment, it is recommended that you deploy at least three machine sets to hold infrastructure components. Both OpenShift Logging and {SMProductName} deploy Elasticsearch, which requires three instances to be installed on different nodes. Each of these nodes can be deployed to different availability zones for high availability. This configuration requires three different machine sets, one for each availability zone. In global Azure regions that do not have multiple availability zones, you can use availability sets to ensure high availability.
[NOTE]
====
After adding the `NoSchedule` taint on the infrastructure node, existing DNS pods running on that node are marked as `misscheduled`. You must either delete or link:https://access.redhat.com/solutions/6592171[add toleration on `misscheduled` DNS pods].

4
nodes/pods/nodes-pods-vertical-autoscaler.adoc
View File

@@ -41,10 +41,6 @@ include::modules/nodes-pods-vertical-autoscaler-install.adoc[leveloffset=+1]
include::modules/nodes-pods-vertical-autoscaler-moving-vpa.adoc[leveloffset=+1]
.Additional resources
* xref:../../machine_management/creating-infrastructure-machinesets.adoc#creating-infrastructure-machinesets-production[Creating infrastructure machine sets]
include::modules/nodes-pods-vertical-autoscaler-using-about.adoc[leveloffset=+1]
include::modules/nodes-pods-vertical-autoscaler-tuning.adoc[leveloffset=+2]