Skip to content

Commit 8d95176

Browse files
authored
Merge pull request #100843 from tedaveryredhat/OSDOCS-15557
OSDOCS-15557:Update attributes and comp table in MicroShift v4.21
2 parents 95c3bc1 + c2bb706 commit 8d95176

File tree

5 files changed

+22
-13
lines changed

5 files changed

+22
-13
lines changed

_attributes/attributes-microshift.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
:experimental:
55
:imagesdir: images
66
:OCP: OpenShift Container Platform
7-
:ocp-version: 4.20
7+
:ocp-version: 4.21
88
:oc-first: pass:quotes[OpenShift CLI (`oc`)]
99
:ai-first: artificial intelligence (AI)
1010
//OpenShift Kubernetes Engine
@@ -16,7 +16,7 @@
1616
:gitops-title: Red{nbsp}Hat OpenShift GitOps
1717
:gitops: GitOps
1818
:product-registry: OpenShift image registry
19-
:product-version: 4.20
19+
:product-version: 4.21
2020
:rhel-major: rhel-9
2121
:rhoai-full: Red{nbsp}Hat OpenShift AI
2222
:rhoai: RHOAI
@@ -32,6 +32,6 @@
3232
:op-system-bundle: Red{nbsp}Hat Device Edge
3333
:ovms: OpenVINO Model Server
3434
:ov: OVMS
35-
:rpm-repo-version: rhocp-4.20
35+
:rpm-repo-version: rhocp-4.21
3636
:rhde-version: 4
3737
:VirtProductName: OpenShift Virtualization

microshift_cli_ref/microshift-usage-oc-kubectl.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The additional command `oc new-app`, for example, makes it easier to get new app
3535
If you installed an earlier version of `oc`, you might not be able use it to complete all of the commands in {microshift-short} {product-version}. If you want the latest features, you must download and install the latest version of `oc` that corresponds with your {microshift-short} version.
3636
====
3737

38-
Using new capabilities often requires the latest `oc` binary. A 4.20 server might have additional capabilities that a 4.16 `oc` binary cannot use and a 4.20 `oc` binary might have additional capabilities that are unsupported by a 4.15 server.
38+
Using new capabilities often requires the latest `oc` binary. A 4.21 server might have additional capabilities that a 4.16 `oc` binary cannot use and a 4.21 `oc` binary might have additional capabilities that are unsupported by a 4.15 server.
3939

4040
.Compatibility Matrix
4141

modules/microshift-embed-microshift-image-offline-deploy.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ include::snippets/microshift-rhel10-bootc-not-osbuild.adoc[leveloffset=1]
3434
----
3535
$ sudo dnf install -y microshift-release-info-_<release_version>_
3636
----
37-
Replace `_<release_version>_` with the numerical value of the release you are deploying, using the entire version number, such as `4.20.1`.
37+
Replace `_<release_version>_` with the numerical value of the release you are deploying, using the entire version number, such as `4.21.1`.
3838

3939
.. List the contents of the `/usr/share/microshift/release` directory to verify the presence of the release information files by running the following command:
4040
+
@@ -65,7 +65,7 @@ $ sudo dnf download microshift-release-info-_<release_version>_ # <1>
6565
.Example RPM output
6666
[source,terminal,subs="+quotes"]
6767
----
68-
microshift-release-info-4.20.1.-202512101230.p0.g7dc6a00.assembly.4.20.1.el9.noarch.rpm
68+
microshift-release-info-4.21.1.-202512101230.p0.g7dc6a00.assembly.4.21.1.el9.noarch.rpm
6969
----
7070

7171
.. Unpack the RPM package without installing it by running the following command:

modules/microshift-updating-rpms-z.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
= Applying patch updates using RPMs
88

99
[role="_abstract"]
10-
Updating {microshift-short} on non `rpm-ostree` systems such as {op-system-base-full} requires downloading then updating the RPMs. For example, use the following procedure to upgrade from 4.20.1 to 4.20.2.
10+
Updating {microshift-short} on non `rpm-ostree` systems such as {op-system-base-full} requires downloading then updating the RPMs. For example, use the following procedure to upgrade from 4.21.1 to 4.21.2.
1111

1212
include::snippets/microshift-unsupported-config-warn.adoc[leveloffset=+1]
1313

snippets/microshift-rhde-compatibility-table-snip.adoc

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,28 @@
99

1010
{op-system-base-full} and {microshift-short} work together as a single solution for device-edge computing. You can update each component separately, but the product versions must be compatible. Supported configurations of {op-system-bundle} use verified releases for each together as listed in the following table:
1111

12+
[NOTE]
13+
====
14+
Be sure to check the support status of a release on the product lifecycle page.
15+
====
16+
1217
[%header,cols="3",cols="1,1,2"]
1318
|===
1419
^|*{op-system-base} Version(s)*
1520
^|*{microshift-short} Version*
1621
^|*Supported {microshift-short} Version{nbsp}&#8594;{nbsp}Version Updates*
1722

23+
^|10.0
24+
^|4.21
25+
^|4.21.0{nbsp}&#8594;{nbsp}4.21.z (Technology Preview)
26+
27+
^|9.6
28+
^|4.21
29+
^|4.21.0{nbsp}&#8594;{nbsp}4.21.z
30+
1831
^|9.6
1932
^|4.20
20-
^|4.20.0{nbsp}&#8594;{nbsp}4.20.z
33+
^|4.20.0{nbsp}&#8594;{nbsp}4.20.z, 4.20{nbsp}&#8594;{nbsp}4.21
2134

2235
^|9.6
2336
^|4.19
@@ -35,11 +48,7 @@
3548
^|4.16
3649
^|4.16.0{nbsp}&#8594;{nbsp}4.16.z, 4.16{nbsp}&#8594;{nbsp}4.17, 4.16{nbsp}&#8594;{nbsp}4.18
3750

38-
^|9.2
39-
^|4.15
40-
^|4.15.0{nbsp}&#8594;{nbsp}4.15.z, 4.15{nbsp}&#8594;{nbsp}4.16 on {op-system-base} 9.4
41-
4251
^|9.2
4352
^|4.14
44-
^|4.14.0{nbsp}&#8594;{nbsp}4.14.z, 4.14{nbsp}&#8594;{nbsp}4.15, 4.14{nbsp}&#8594;{nbsp}4.16 on {op-system-base} 9.4
53+
^|4.14.0{nbsp}&#8594;{nbsp}4.14.z, 4.14{nbsp}&#8594;{nbsp}4.16 on {op-system-base} 9.4
4554
|===

0 commit comments

Comments
 (0)