mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
Merge pull request #78043 from bergerhoffer/OCPBUILD-7-rn
Adding notable technical change for builder sa
This commit is contained in:
@@ -1366,6 +1366,14 @@ In {product-title} {product-version}, {olmv1-first} changes its default upgrade
|
||||
|
||||
For more information, see xref:../release_notes/ocp-4-16-release-notes.adoc#ocp-4-16-olmv1-legacy-olm-upgrade-edges_release-notes[Support for {olmv0} upgrade edges in {olmv1} (Technology Preview)].
|
||||
|
||||
[discrete]
|
||||
[id="ocp-4-16-builder-sa"]
|
||||
=== The builder service account is no longer created if the Build cluster capability is disabled
|
||||
|
||||
With this release, if you disable the `Build` cluster capability, the `builder` service account and its corresponding secrets are no longer created.
|
||||
|
||||
For more information, see xref:../installing/cluster-capabilities.adoc#build-config-capability_cluster-capabilities[Build capability].
|
||||
|
||||
[id="ocp-4-16-deprecated-removed-features_{context}"]
|
||||
== Deprecated and removed features
|
||||
|
||||
@@ -2411,7 +2419,7 @@ To retain the catalog rebuilding functionality, use `--rebuild-catalog`. However
|
||||
|
||||
* Previously, when running a cluster with FIPS enabled, you might have received the following error when running the {oc-first} on a {op-system-base} 9 system: `FIPS mode is enabled, but the required OpenSSL backend is unavailable`. With this release, the default version of OpenShift CLI (`oc`) is compiled with {op-system-base-full} 9 and works properly when running a cluster with FIPS enabled on {op-system-base} 9. Additionally, a version of `oc` compiled with {op-system-base} 8 is also provided, which must be used if you are running a cluster with FIPS enabled on {op-system-base} 8. (link:https://issues.redhat.com/browse/OCPBUGS-23386[*OCPBUGS-23386*], link:https://issues.redhat.com/browse/OCPBUGS-28540[*OCPBUGS-28540*])
|
||||
|
||||
* Previously, role bindings related to the `ImageRegistry`, `Build`, and `DeploymentConfig` capabilities were created in every namespace, even if the capability was disabled. With this release, the role bindings are only created if the cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*])
|
||||
* Previously, role bindings related to the `ImageRegistry` and `Build` capabilities were created in every namespace, even if the capability was disabled. With this release, the role bindings are only created if the respective cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*])
|
||||
|
||||
* Previously, during the disk-to-mirror process for fully disconnected environments, oc-mirror plugin v1 would fail to mirror the catalog image when access to Red Hat registries was blocked. Additionally, if the `ImageSetConfiguration` used a `targetCatalog` for the mirrored catalog, mirroring would fail due to incorrect catalog image references regardless of the workflow. This issue has been resolved by updating the catalog image source for mirroring to the mirror registry. (link:https://issues.redhat.com/browse/OCPBUGS-34646[*OCPBUGS-34646*])
|
||||
|
||||
|
||||
Reference in New Issue
Block a user