You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* xref:../../installing/installing_aws/ipi/installing-aws-customizations.adoc#installing-aws-customizations[Installing a cluster on AWS with customizations]
24
25
* xref:../../installing/installing_gcp/installing-gcp-customizations.adoc#installing-gcp-customizations[Installing a cluster on {gcp-short} with customizations]
* xref:../../installing/installing_bare_metal/ipi/ipi-install-overview.adoc#ipi-install-overview[Deploying installer-provisioned clusters on bare metal]
38
41
* xref:../../installing/installing_bare_metal/preparing-to-install-on-bare-metal.adoc#preparing-to-install-on-bare-metal[Preparing for bare metal cluster installation]
39
42
* xref:../../installing/installing_bare_metal/bare-metal-postinstallation-configuration.adoc#bmo-config-using-bare-metal-operator_bare-metal-postinstallation-configuration[Configuration using the Bare Metal Operator]
The Cluster CSI Snapshot Controller Operator is an optional cluster capability that can be disabled by cluster administrators during installation. For more information about optional cluster capabilities, see "Cluster capabilities" in _Installing_.
24
-
====
25
-
26
22
endif::operator-ref[]
27
23
28
24
ifdef::cluster-caps[]
29
-
30
25
The Cluster CSI Snapshot Controller Operator provides the features for the `CSISnapshot` capability.
31
-
32
26
endif::cluster-caps[]
33
27
34
28
The Cluster CSI Snapshot Controller Operator installs and maintains the CSI Snapshot Controller. The CSI Snapshot Controller is responsible for watching the `VolumeSnapshot` CRD objects and manages the creation and deletion lifecycle of volume snapshots.
The Cluster Samples Operator is an optional cluster capability that can be disabled by cluster administrators during installation. For more information about optional cluster capabilities, see "Cluster capabilities" in _Installing_.
26
-
====
27
-
28
24
endif::operator-ref[]
29
25
30
26
ifdef::cluster-caps[]
@@ -57,10 +53,9 @@ The samples resource includes a finalizer, which cleans up the following upon it
57
53
58
54
Upon deletion of the samples resource, the Cluster Samples Operator recreates the resource using the default configuration.
Copy file name to clipboardExpand all lines: modules/ingress-operator.adoc
+15-19Lines changed: 15 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ endif::[]
16
16
ifdef::operator-ref[= Ingress Operator]
17
17
ifdef::cluster-caps[= Ingress Capability]
18
18
19
+
[role="_abstract"]
19
20
ifdef::cluster-caps[]
20
21
The Ingress Operator provides the features for the Ingress Capability. The Ingress Capability is enabled by default.
21
22
@@ -24,25 +25,21 @@ The Ingress Operator provides the features for the Ingress Capability. The Ingre
24
25
If you set the `baselineCapabilitySet` field to `None`, you must explicitly enable the Ingress Capability, because the installation of a cluster fails if the Ingress Capability is disabled.
25
26
====
26
27
endif::cluster-caps[]
27
-
28
28
The Ingress Operator configures and manages the {product-title} router.
$ oc get clusteringresses.ingress.openshift.io -n openshift-ingress-operator default -o yaml
54
51
----
55
52
56
-
57
-
== Notes
58
-
53
+
Notes::
54
+
+
59
55
The Ingress Operator sets up the router in the `openshift-ingress` project and creates the deployment for the router:
60
-
56
+
+
61
57
[source,terminal]
62
58
----
63
59
$ oc get deployment -n openshift-ingress
64
60
----
65
-
61
+
+
66
62
The Ingress Operator uses the `clusterNetwork[].cidr` from the `network/cluster` status to determine what mode (IPv4, IPv6, or dual stack) the managed Ingress Controller (router) should operate in. For example, if `clusterNetwork` contains only a v6 `cidr`, then the Ingress Controller operates in IPv6-only mode.
67
-
63
+
+
68
64
In the following example, Ingress Controllers managed by the Ingress Operator will run in IPv4-only mode because only one cluster network exists and the network is an IPv4 `cidr`:
69
-
65
+
+
70
66
[source,terminal]
71
67
----
72
68
$ oc get network/cluster -o jsonpath='{.status.clusterNetwork[*]}'
Copy file name to clipboardExpand all lines: modules/insights-operator.adoc
+8-19Lines changed: 8 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,40 +16,29 @@ endif::[]
16
16
ifdef::operator-ref[= Insights Operator]
17
17
ifdef::cluster-caps[= Insights capability]
18
18
19
+
[role="_abstract"]
19
20
ifdef::operator-ref[]
20
-
21
-
[NOTE]
22
-
====
23
21
The {insights-operator} is an optional cluster capability that can be disabled by cluster administrators during installation. For more information about optional cluster capabilities, see "Cluster capabilities" in _Installing_.
24
-
====
25
-
26
22
endif::operator-ref[]
27
23
28
24
ifdef::cluster-caps[]
29
-
30
25
The {insights-operator} provides the features for the `Insights` capability.
31
-
32
26
endif::cluster-caps[]
33
27
34
28
The {insights-operator} gathers {product-title} configuration data and sends it to Red{nbsp}Hat. The data is used to produce proactive insights recommendations about potential issues that a cluster might be exposed to. These insights are communicated to cluster administrators through the {red-hat-lightspeed} advisor service on link:https://console.redhat.com/[console.redhat.com].
Copy file name to clipboardExpand all lines: modules/machine-api-capability.adoc
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@
6
6
[id="machine-api-capability_{context}"]
7
7
= Machine API capability
8
8
9
+
[role="_abstract"]
9
10
The `machine-api-operator`, `cluster-autoscaler-operator`, and `cluster-control-plane-machine-set-operator` Operators provide the features for the `MachineAPI` capability. You can disable this capability only if you install a cluster with user-provisioned infrastructure.
10
11
11
12
The Machine API capability is responsible for all machine configuration and management in the cluster. If you disable the Machine API capability during installation, you need to manage all machine-related tasks manually.
Copy file name to clipboardExpand all lines: modules/node-tuning-operator.adoc
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,12 +26,11 @@ ifdef::perf[]
26
26
27
27
endif::perf[]
28
28
ifdef::cluster-caps[= Node Tuning capability]
29
-
29
+
[role="_abstract"]
30
30
ifdef::cluster-caps[]
31
31
The Node Tuning Operator provides features for the `NodeTuning` capability.
32
32
endif::cluster-caps[]
33
33
34
-
[role="_abstract"]
35
34
The Node Tuning Operator helps you manage node-level tuning by orchestrating the TuneD daemon and achieves low latency performance by using the Performance Profile controller. The majority of high-performance applications require some level of kernel tuning. The Node Tuning Operator provides a unified management interface to users of node-level sysctls and more flexibility to add custom tuning specified by user needs.
36
35
37
36
ifdef::cluster-caps[]
@@ -60,8 +59,7 @@ In earlier versions of {product-title}, the Performance Addon Operator was used
0 commit comments