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: modules/images-configuration-parameters.adoc
+29Lines changed: 29 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,35 @@ pods. For instance, whether or not to allow insecure access. It does not contain
47
47
48
48
Either `blockedRegistries` or `allowedRegistries` can be set, but not both.
49
49
50
+
ifndef::openshift-rosa,openshift-dedicated[]
51
+
|`imageStreamImportMode`
52
+
|Controls the import mode behavior of image streams.
53
+
54
+
You must enable the `TechPreviewNoUpgrade` feature set in the `FeatureGate` custom resource (CR) to enable the `imageStreamImportMode` feature.
55
+
For more information about feature gates, see "Understanding feature gates".
56
+
57
+
You can set the `imageStreamImportMode` field to either of the following values:
58
+
59
+
* `Legacy`: Indicates that the legacy behavior must be used. The legacy behavior discards the manifest list and imports a single sub-manifest. In this case, the platform is chosen in the following order of priority:
60
+
. Tag annotations: Determining the platform by using the platform-specific annotations in the image tags.
61
+
. Control plane architecture or the operating system: Selecting the platform based on the architecture or the operating system of the control plane.
62
+
. `linux/amd64`: If no platform is selected by the preceeding methods, the `linux/amd64` platform is selected.
63
+
. The first manifest in the list is selected.
64
+
65
+
* `PreserveOriginal`: Indicates that the original manifest is preserved. The manifest list and its sub-manifests are imported.
66
+
67
+
If you specify a value for this field, the value is applied to the newly created image stream tags that do not already have this value manually set.
68
+
69
+
If you do not configure this field, the behavior is decided based on the payload type advertised by the `ClusterVersion` status. In this case, the platform is chosen as follows:
70
+
71
+
* The single architecture payload implies that the `Legacy` mode is applicable.
72
+
* The multi payload implies that the `PreserveOriginal` mode is applicable.
73
+
74
+
For information about importing manifest lists, see "Working with manifest lists".
Copy file name to clipboardExpand all lines: modules/nodes-cluster-enabling-features-about.adoc
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@ The following Technology Preview features are enabled by this feature set:
28
28
** Dynamic Resource Allocation API. Enables a new API for requesting and sharing resources between pods and containers. This is an internal feature that most users do not need to interact with. (`DynamicResourceAllocation`)
29
29
** Pod security admission enforcement. Enables the restricted enforcement mode for pod security admission. Instead of only logging a warning, pods are rejected if they violate pod security standards. (`OpenShiftPodSecurityAdmission`)
30
30
** StatefulSet pod availability upgrading limits. Enables users to define the maximum number of statefulset pods unavailable during updates which reduces application downtime. (`MaxUnavailableStatefulSet`)
31
+
** Image mode behavior of image streams. Enables a new API for controlling the import mode behavior of image streams. (`imageStreamImportMode`)
31
32
**`OVNObservability` resource allows you to verify expected network behavior. Supports the following network APIs: `NetworkPolicy`, `AdminNetworkPolicy`, `BaselineNetworkPolicy`, `UserDefinesdNetwork` isolation, multicast ACLs, and egress firewalls. When enabled, you can view network events in the terminal.
0 commit comments