Skip to content

Commit 26ead18

Browse files
committed
OSDOCS-5526: Update internal image streams in multi-arch docs
1 parent 5e32753 commit 26ead18

File tree

2 files changed

+14
-14
lines changed

2 files changed

+14
-14
lines changed

modules/multi-architecture-import-imagestreams.adoc

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
//Module included in the following assemblies
22
//
3-
//post_installation_configuration/cluster-tasks.adoc
3+
//post_installation_configuration/multi-architecture-configuration.adoc
44

55
:_content-type: PROCEDURE
66
[id="multi-architecture-import-imagestreams_{context}"]
@@ -9,16 +9,6 @@
99

1010
On an {product-title} {product-version} cluster with multi-architecture compute machines, the image streams in the cluster do not import manifest lists automatically. You must manually change the default `importMode` option to the `PreserveOriginal` option in order to import the manifest list.
1111

12-
[IMPORTANT]
13-
====
14-
The `referencePolicy.type` field of your `ImageStream` object must be set to the `Source` type for this procedure to run successfully.
15-
[source,yaml]
16-
----
17-
referencePolicy:
18-
type: Source
19-
----
20-
====
21-
2212
.Prerequisites
2313

2414
* You installed the {product-title} CLI (`oc`).
@@ -29,7 +19,7 @@ referencePolicy:
2919
+
3020
[source,terminal]
3121
----
32-
oc patch is/cli-artifacts -n openshift -p '{"spec":{"tags":[{"name":"latest","importPolicy":{"importMode":"PreserveOriginal"}}]}}'
22+
$ oc patch is/cli-artifacts -n openshift -p '{"spec":{"tags":[{"name":"latest","importPolicy":{"importMode":"PreserveOriginal"}}]}}'
3323
----
3424

3525
.Verification
@@ -38,7 +28,7 @@ oc patch is/cli-artifacts -n openshift -p '{"spec":{"tags":[{"name":"latest","im
3828
+
3929
[source,terminal]
4030
----
41-
oc get istag cli-artifacts:latest -n openshift -oyaml
31+
$ oc get istag cli-artifacts:latest -n openshift -oyaml
4232
----
4333

4434
+

post_installation_configuration/multi-architecture-configuration.adoc

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,17 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
An {product-title} cluster with multi-architecture compute machines is a cluster that supports compute machines with different architectures. Clusters with multi-architecture compute machines are available only on AWS or Azure installer-provisioned infrastructures and bare metal user-provisioned infrastructures with `x86_64` control plane machines.
9+
An {product-title} cluster with multi-architecture compute machines is a cluster that supports compute machines with different architectures. Clusters with multi-architecture compute machines are available only on AWS or Azure installer-provisioned infrastructures and bare metal user-provisioned infrastructures with `x86_64` control plane machines.
10+
11+
[NOTE]
12+
====
13+
When there are nodes with multiple architectures in your cluster, the architecture of your image must be consistent with the architecture of the node. You need to ensure that the pod is assigned to the node with the appropriate architecture and that it matches the image architecture. For more information on assigning pods to nodes, see link:https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/[Assigning pods to nodes].
14+
====
15+
16+
[IMPORTANT]
17+
====
18+
The Cluster Samples Operator is not supported on clusters with multi-architecture compute machines. Your cluster can be created without this capability. For more information, see xref:../post_installation_configuration/enabling-cluster-capabilities.adoc#enabling-cluster-capabilities[Enabling cluster capabilities]
19+
====
1020

1121
== Creating a cluster with multi-architecture compute machine on Azure
1222

0 commit comments

Comments
 (0)