|
| 1 | +[id="sandboxed-containers-4-9-release-notes"] |
| 2 | += {sandboxed-containers-first} {product-version} release notes |
| 3 | +include::modules/common-attributes.adoc[] |
| 4 | +:context: sandboxed-containers-release-notes |
| 5 | + |
| 6 | +toc::[] |
| 7 | + |
| 8 | +[id="ocp-4-9-about-this-release"] |
| 9 | +== About this release |
| 10 | + |
| 11 | +These release notes track the development of {sandboxed-containers-first} in Red Hat {product-title}. |
| 12 | + |
| 13 | +This product is currently in Technology Preview. {sandboxed-containers-first} is not intended for production use. For more information, see the Red Hat Customer Portal link:https://access.redhat.com/support/offerings/techpreview[support scope] for features in Technology Preview. |
| 14 | + |
| 15 | +[id="sandboxed-containers-4-9-new-features-and-enhancements"] |
| 16 | +== New features and enhancements |
| 17 | + |
| 18 | +[id="fips-compatability-rn"] |
| 19 | +=== FIPS compatibility |
| 20 | + |
| 21 | +FIPS mode is now automatically enabled for {sandboxed-containers-first}. {sandboxed-containers-first} deployed on an {product-title} cluster installed in FIPS mode will not taint the cluster's FIPS support. For more information, see xref:../sandboxed_containers/understanding-sandboxed-containers.adoc#security-compliance-nist_understanding-sandboxed-containers[Understanding compliance and risk management]. |
| 22 | + |
| 23 | +[id="collect-resources-with-must-gather-rn"] |
| 24 | +=== Collect resources with must-gather |
| 25 | + |
| 26 | +The {sandboxed-containers-operator} now includes a must-gather image, allowing you to collect custom resources and log files specific to this Operator and the underlying runtime components for diagnostic purposes. For more information, see xref:../sandboxed_containers/troubleshooting-sandboxed-containers.adoc#troubleshooting-sandboxed-containers[Collecting {sandboxed-containers-first} data for Red Hat Support]. |
| 27 | + |
| 28 | +[id="sandboxed-containers-disconnected-environments-rn"] |
| 29 | +=== Disconnected environments |
| 30 | + |
| 31 | +You can now install the {sandboxed-containers-operator} in a disconnected environment. For more information, see the xref:../sandboxed_containers/deploying-sandboxed-container-workloads.adoc#deploying-sandboxed-containers-workloads_additional-resources[Additional resources for Deploying {sandboxed-containers-first} workloads]. |
| 32 | + |
| 33 | +[id="sandboxed-containers-4-9-bug-fixes"] |
| 34 | +== Bug fixes |
| 35 | + |
| 36 | +* Previously, when running Fedora on {sandboxed-containers-first}, some packages required file access permission changes that {product-title} did not grant to containers by default. With this release, these permissions are granted by default. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1915377[*BZ#1915377*]) |
| 37 | + |
| 38 | +* Previously, adding a value to `kataConfgPoolSelector` in the {product-title} web console populated `scheduling.nodeSelector` with an empty value. As a result, pods that used a `RuntimeClass` object with the value of `kata` could be scheduled to nodes without the Kata Containers runtime installed. With this release, only nodes labeled with the same label as defined in `kataConfgPoolSelector` will install the Kata Containers runtime. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2019384[*BZ#2019384*]) |
| 39 | + |
| 40 | +* Previously, the {sandboxed-containers-operator} details page on Operator Hub was missing fields. In this release, these fields are no longer missing. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2019383[*BZ#2019383*]) |
| 41 | + |
| 42 | +* Previously, creating multiple `KataConfig` custom resources resulted in a silent failure, with no error from the {product-title} web console notifying the user that creating more than one custom resource failed. With this release, the user receives an error when trying to create multiple custom resources. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2019381[*BZ#2019381*]) |
| 43 | + |
| 44 | +* Previously, there were instances where the Operator Hub in the {product-title} web console did not display icons for an Operator. With this release, icons are always displayed. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2019380[*BZ#9019380*]) |
| 45 | + |
| 46 | +[id="sandboxed-containers-4-9-known-issues"] |
| 47 | +== Known issues |
| 48 | + |
| 49 | +* If you are using {sandboxed-containers-first}, you cannot use the `hostPath` volume in a {product-title} cluster to mount a file or directory from the host node’s file system into your pod. As an alternative, you can use local persistent volumes. See xref:../storage/persistent_storage/persistent-storage-local.adoc[Persistent storage using local volumes] for more information. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1904609[*BZ#1904609*]) |
| 50 | + |
| 51 | +[id="sandboxed-containers-4-9-asynchronous-errata-updates"] |
| 52 | +== Asynchronous errata updates |
| 53 | + |
| 54 | +Security, bug fix, and enhancement updates for {sandboxed-containers-first} {product-version} are released as asynchronous errata through the Red Hat Network. All {product-title} {product-version} errata is https://access.redhat.com/downloads/content/290/[available on the Red Hat Customer Portal]. See the https://access.redhat.com/support/policy/updates/openshift[{product-title} Life Cycle] for more information about asynchronous errata. |
| 55 | + |
| 56 | +Red Hat Customer Portal users can enable errata notifications in the account settings for Red Hat Subscription Management (RHSM). When errata notifications are enabled, users are notified via email whenever new errata relevant to their registered systems are released. |
| 57 | + |
| 58 | +[NOTE] |
| 59 | +==== |
| 60 | +Red Hat Customer Portal user accounts must have systems registered and consuming {product-title} entitlements for {product-title} errata notification emails to generate. |
| 61 | +==== |
| 62 | + |
| 63 | +This section will continue to be updated over time to provide notes on enhancements and bug fixes for future asynchronous errata releases of {sandboxed-containers-first} 1.1.0. |
| 64 | + |
| 65 | +[id="sandboxed-containers-1-1-0"] |
| 66 | +=== RHEA-2021:3941 - {sandboxed-containers-first} 1.1.0 image release, bug fix,and enhancement advisory |
| 67 | + |
| 68 | +Issued: 2021-10-21 |
| 69 | + |
| 70 | +{sandboxed-containers-first} release 1.1.0 is now available. This advisory contains an update for {sandboxed-containers-first} with enhancements and bug fixes. |
| 71 | + |
| 72 | +The list of bug fixes included in the update is documented in the link:https://access.redhat.com/errata/RHEA-2021:3941[RHEA-2021:3941] advisory. |
| 73 | +// |
| 74 | +//#link:https://access.redhat.com/errata/product/290/ver=4.9/rhel---8/x86_64/RHEA-2021:3941[] |
| 75 | +// |
| 76 | +//[id="sandboxed-containers-1-0-2"] |
| 77 | +//=== RHBA-2021:3751 - {sandboxed-containers-first} 1.0.2 bug fix advisory |
| 78 | +// |
| 79 | +//Issued: 2021-10-07 |
| 80 | +// |
| 81 | +//{sandboxed-containers-first} release 1.0.2 is now available. This advisory contains an update for {sandboxed-containers-first} with bug fixes. |
| 82 | +// |
| 83 | +//The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/product/290/ver=4.8/rhel---8/x86_64/RHBA-2021:3751[RHBA-2021:3751] advisory. |
0 commit comments