Skip to content

Commit 3ef28d9

Browse files
authored
Merge pull request #96507 from mburke5678/mco-ocl-418-backport-rn
MCO Backport OCL to 4.18 RN
2 parents 993e96b + b9d49a3 commit 3ef28d9

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

release_notes/ocp-4-18-release-notes.adoc

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2396,7 +2396,7 @@ In the following tables, features are marked with the following statuses:
23962396
|On-cluster RHCOS image layering
23972397
|Technology Preview
23982398
|Technology Preview
2399-
|Technology Preview
2399+
|General Availability
24002400

24012401
|Node disruption policies
24022402
|Technology Preview
@@ -3040,6 +3040,26 @@ You can view the container images in this release by running the following comma
30403040
$ oc adm release info 4.18.20 --pullspecs
30413041
----
30423042

3043+
[id="ocp-4-18-20-new-features-and-enhancements_{context}"]
3044+
==== New features and enhancements
3045+
3046+
[id="ocp-4-18-20-updating-machine-config-operator-ocl_{context}"]
3047+
===== On-cluster layering changes is now generally available
3048+
There are several important changes to the on-cluster layering feature:
3049+
3050+
* The API version is now `machineconfiguration.openshift.io/v1`. The new version includes the following changes:
3051+
** The `baseImagePullSecret` parameter is now optional. If not specified, the default `global-pull-secret-copy` is used.
3052+
** The `buildInputs` parameter is no longer required. All parameters previously under the `buildInputs` parameter are promoted one level.
3053+
** The `containerfileArch` parameter now supports multiple architectures. Previously, only `noarch` was supported.
3054+
** The required `imageBuilderType` is now `Job`. Previously, the required builder was `PodImageBuilder`.
3055+
** The `renderedImagePushspec` parameter is now `renderedImagePushSpec`.
3056+
** The `buildOutputs` and `currentImagePullSecret` parameters are no longer required.
3057+
* You can manually rebuild your custom layered image by applying an annotation to the `MachineOSConfig` object.
3058+
* You can now automatically delete an on-cluster custom layered image by deleting the associated `MachineOSBuild` object.
3059+
* On-cluster layering is now supported in disconnected environments.
3060+
3061+
For more information, see xref:../machine_configuration/mco-coreos-layering.adoc#coreos-layering-configuring-on_mco-coreos-layering[Using on-cluster layering to apply a custom layered image].
3062+
30433063
[id="ocp-4-18-20-bug-fixes_{context}"]
30443064
==== Bug fixes
30453065

0 commit comments

Comments
 (0)