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
===== 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].
0 commit comments