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
Copy file name to clipboardExpand all lines: installing/installing-fips.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,13 @@ Because FIPS must be enabled before the operating system that your cluster uses
26
26
|Attributes
27
27
|Limitations
28
28
29
-
|FIPS support in {op-system-base} 7, {op-system-base} 8, and {op-system} operating systems.
29
+
|FIPS support in {op-system-base} 8 and {op-system} operating systems.
30
30
.3+|The FIPS implementation does not offer a single function that both computes hash functions and validates the keys that are based on that hash. This limitation will continue to be evaluated and improved in future {product-title} releases.
31
31
32
32
|FIPS support in CRI-O runtimes.
33
33
|FIPS support in {product-title} services.
34
34
35
-
|FIPS Validated / Modules in Process cryptographic module and algorithms that are obtained from {op-system-base} 7, {op-system-base} 8, and {op-system} binaries and images.
35
+
|FIPS Validated / Modules in Process cryptographic module and algorithms that are obtained from {op-system-base} 8 and {op-system} binaries and images.
36
36
|
37
37
38
38
|Use of FIPS compatible golang compiler.
@@ -84,4 +84,4 @@ If you are using Azure File storage, you cannot enable FIPS mode.
84
84
85
85
To apply `AES CBC` encryption to your etcd data store, follow the xref:../security/encrypting-etcd.adoc#encrypting-etcd[Encrypting etcd data] process after you install your cluster.
86
86
87
-
If you add {op-system-base} nodes to your cluster, ensure that you enable FIPS mode on the machines before their initial boot. See xref:../machine_management/adding-rhel-compute.adoc#adding-rhel-compute[Adding RHEL compute machines to an {product-title} cluster] and link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-federal_standards_and_regulations#sec-Enabling-FIPS-Mode[Enabling FIPS Mode] in the {op-system-base} 7 documentation or link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#enabling-fips-mode-in-a-container_using-the-system-wide-cryptographic-policies[Enabling FIPS Mode] in the {op-system-base} 8 documentation
87
+
If you add {op-system-base} nodes to your cluster, ensure that you enable FIPS mode on the machines before their initial boot. See xref:../machine_management/adding-rhel-compute.adoc#adding-rhel-compute[Adding RHEL compute machines to an {product-title} cluster] and link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#enabling-fips-mode-in-a-container_using-the-system-wide-cryptographic-policies[Enabling FIPS Mode] in the {op-system-base} 8 documentation.
Copy file name to clipboardExpand all lines: modules/creating-machines-bare-metal.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ To install {op-system} on the machines, follow either the steps to use an ISO im
13
13
14
14
[NOTE]
15
15
====
16
-
The compute node deployment steps included in this installation document are {op-system}-specific. If you choose instead to deploy {op-system-base}-based compute nodes, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of {op-system-base} 7 compute machines is deprecated and planned for removal in a future release of {product-title} 4.
16
+
The compute node deployment steps included in this installation document are {op-system}-specific. If you choose instead to deploy {op-system-base}-based compute nodes, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Only {op-system-base} 8 compute machines are supported.
17
17
====
18
18
19
19
You can configure {op-system} during ISO and PXE installations by using the following methods:
Copy file name to clipboardExpand all lines: modules/installation-requirements-user-infra.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ these cluster machines.
99
99
endif::ibm-z[]
100
100
====
101
101
102
-
The bootstrap and control plane machines must use {op-system-first} as the operating system. However, the compute machines can choose between {op-system-first}, {op-system-base-full} 7.9, or {op-system-base} 8.4.
102
+
The bootstrap and control plane machines must use {op-system-first} as the operating system. However, the compute machines can choose between {op-system-first}, {op-system-base} 8.4, or {op-system-base} 8.5.
103
103
104
104
ifndef::openshift-origin[]
105
105
Note that {op-system} is based on {op-system-base-full} 8 and inherits all of its hardware certifications and requirements.
@@ -169,7 +169,7 @@ endif::ibm-z[]
169
169
ifndef::openshift-origin[]
170
170
|Compute
171
171
ifdef::ibm-z,ibm-power[|{op-system}]
172
-
ifndef::ibm-z,ibm-power[|{op-system}, {op-system-base} 7.9, or {op-system-base} 8.4 ^[3]^]
172
+
ifndef::ibm-z,ibm-power[|{op-system}, {op-system-base} 8.4, or {op-system-base} 8.5 ^[3]^]
173
173
|2
174
174
|8 GB
175
175
|100 GB
@@ -208,7 +208,7 @@ ifndef::ibm-z,bare-metal[]
208
208
endif::ibm-z,bare-metal[]
209
209
ifndef::ibm-z[]
210
210
2. {product-title} and Kubernetes are sensitive to disk performance, and faster storage is recommended, particularly for etcd on the control plane nodes which require a 10 ms p99 fsync duration. Note that on many cloud platforms, storage size and IOPS scale together, so you might need to over-allocate storage volume to obtain sufficient performance.
211
-
3. As with all user-provisioned installations, if you choose to use {op-system-base} compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks. Use of {op-system-base} 7 compute machines is deprecated and planned for removal in a future release of {product-title} 4.
211
+
3. As with all user-provisioned installations, if you choose to use {op-system-base} compute machines in your cluster, you take responsibility for all operating system life cycle management and maintenance, including performing system updates, applying patches, and completing all other required tasks.
Copy file name to clipboardExpand all lines: modules/rhel-compute-requirements.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,17 +19,17 @@ ifdef::openshift-origin[]
19
19
** Base OS: CentOS 7.4.
20
20
endif::[]
21
21
ifdef::openshift-enterprise,openshift-webscale[]
22
-
** Base OS: link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/installation_guide/index[{op-system-base} 7.9] or link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/index[{op-system-base} 8.4] with "Minimal" installation option.
22
+
** Base OS: link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/index[{op-system-base} 8.4 or 8.5] with "Minimal" installation option.
23
23
+
24
24
[IMPORTANT]
25
25
====
26
-
Adding {op-system-base} 7 compute machines to an {product-title} cluster is deprecated. Deprecated functionality is still included in {product-title} and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.
26
+
Adding {op-system-base} 7 compute machines to an {product-title} cluster is not supported.
27
27
28
-
In addition, you cannot upgrade your {op-system-base} 7 compute machines to {op-system-base} 8. You must deploy new {op-system-base} 8 hosts, and the old {op-system-base} 7 hosts should be removed. See the "Deleting nodes" section for more information.
28
+
If you have {op-system-base} 7 compute machines that were previously supported in a past {product-title} version, you cannot upgrade them to {op-system-base} 8. You must deploy new {op-system-base} 8 hosts, and the old {op-system-base} 7 hosts should be removed. See the "Deleting nodes" section for more information.
29
29
30
30
For the most recent list of major functionality that has been deprecated or removed within {product-title}, refer to the _Deprecated and removed features_ section of the {product-title} release notes.
31
31
====
32
-
** If you deployed {product-title} in FIPS mode, you must enable FIPS on the {op-system-base} machine before you boot it. See link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-federal_standards_and_regulations#sec-Enabling-FIPS-Mode[Enabling FIPS Mode] in the {op-system-base} 7 documentation.
32
+
** If you deployed {product-title} in FIPS mode, you must enable FIPS on the {op-system-base} machine before you boot it. See link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening[Installing a RHEL 8 system with FIPS mode enabled] in the {op-system-base} 8 documentation.
Copy file name to clipboardExpand all lines: modules/rhel-compute-updating.adoc
+16-39Lines changed: 16 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ After you update your cluster, you must update the {op-system-base-full} compute
10
10
11
11
[IMPORTANT]
12
12
====
13
-
{op-system-base-full} version 7.9 and version 8.4 is supported for {op-system-base} worker (compute) machines.
13
+
{op-system-base-full} versions 8.4 and 8.5 are supported for {op-system-base} compute machines.
14
14
====
15
15
16
16
You can also update your compute machines to another minor version of {product-title} if you are using {op-system-base} as the operating system. You do not need to exclude any RPM packages from {op-system-base} when performing a minor version update.
@@ -20,8 +20,6 @@ You can also update your compute machines to another minor version of {product-t
20
20
You cannot upgrade {op-system-base} 7 compute machines to {op-system-base} 8. You must deploy new {op-system-base} 8 hosts, and the old {op-system-base} 7 hosts should be removed.
21
21
====
22
22
23
-
// TODO: This module needs to be updated to reflect RHEL 8 compute machines in 4.10. Because initial support for RHEL 8 starts in 4.9, and upgrading RHEL 7 -> 8 in-place is not supported, this is being left to reflect RHEL 7 upgrades.
24
-
25
23
.Prerequisites
26
24
27
25
* You updated your cluster.
@@ -54,10 +52,10 @@ By default, the base OS RHEL with "Minimal" installation option enables firewall
Note which machine has the `NotReady,SchedulingDisabled` status.
101
76
102
-
.. Review your Ansible inventory file at `/<path>/inventory/hosts` and update its contents so that only the machine with the `NotReady,SchedulingDisabled` status is listed in the `[workers]` section, as shown in the following example:
77
+
.. Review your Ansible inventory file at `/<path>/inventory/hosts` and update its contents so that the {op-system-base} 8 machines are listed in the `[workers]` section, as shown in the following example:
. Optional: Update the operating system packages that were not updated by the `upgrade` playbook. To update packages that are not on {product-version}, use the following command:
0 commit comments