|
|
|
|
@@ -1,5 +1,5 @@
|
|
|
|
|
:_content-type: ASSEMBLY
|
|
|
|
|
[id="microshift-4-13-release-notes"]
|
|
|
|
|
[id="microshift-4-14-release-notes"]
|
|
|
|
|
= {product-title} {product-version} release notes
|
|
|
|
|
include::_attributes/attributes-microshift.adoc[]
|
|
|
|
|
:context: release-notes
|
|
|
|
|
@@ -10,27 +10,22 @@ toc::[]
|
|
|
|
|
|
|
|
|
|
{product-title} is designed to make control plane restarts economical and be lifecycle-managed as a single unit by the operating system. Updates, roll-backs, and configuration changes consist of simply staging another version in parallel and then - without relying on a network - flipping to and from that version and restarting.
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-about-this-release"]
|
|
|
|
|
[id="microshift-4-14-about-this-release"]
|
|
|
|
|
== About this release
|
|
|
|
|
|
|
|
|
|
The Red Hat build of {product-title} is Technology Preview only. Features and known issues that pertain to {product-title} {ocp-version} are included in this topic. This Technology Preview software is not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using {product-title} in production. Technology Preview provides early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
|
|
|
|
|
//The Red Hat build of {product-title} is Technology Preview only. Features and known issues that pertain to {product-title} {ocp-version} are included in this topic. This Technology Preview software is not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using {product-title} in production. Technology Preview provides early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
|
|
|
|
|
|
|
|
|
|
For more information about the support scope of Red Hat Technology Preview features, read link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
|
|
|
|
|
//For more information about the support scope of Red Hat Technology Preview features, read link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
|
|
|
|
|
|
|
|
|
|
//need messaging and link here
|
|
|
|
|
|
|
|
|
|
[IMPORTANT]
|
|
|
|
|
====
|
|
|
|
|
Red Hat does not support an update path from the Technology Preview version to later versions of {product-title}. A new installation is necessary.
|
|
|
|
|
====
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-new-features-and-enhancements"]
|
|
|
|
|
[id="microshift-4-14-new-features-and-enhancements"]
|
|
|
|
|
== New features and enhancements
|
|
|
|
|
|
|
|
|
|
This release adds improvements related to the following components and concepts.
|
|
|
|
|
|
|
|
|
|
//L3 major categories with features in each as L4s, for example:
|
|
|
|
|
[id="microshift-4-13-rhel-edge"]
|
|
|
|
|
[id="microshift-4-14-rhel-edge"]
|
|
|
|
|
=== {op-system-ostree-first} {op-system-version}
|
|
|
|
|
* {product-title} runs on {op-system-ostree} version {op-system-version} or later.
|
|
|
|
|
|
|
|
|
|
@@ -41,74 +36,52 @@ This release adds improvements related to the following components and concepts.
|
|
|
|
|
** If you run cAdvisor as a standalone DaemonSet for monitoring pods and containers, update it to v0.43.0 or later.
|
|
|
|
|
** If you deploy Java applications with the JDK, ensure you are using JDK 11.0.16 and later or JDK 15 and later, which fully support cgroup v2.
|
|
|
|
|
|
|
|
|
|
//[id="microshift-4-13-new-feat-based-on-{op-system-ostree}"]
|
|
|
|
|
//[id="microshift-4-14-new-feat-based-on-{op-system-ostree}"]
|
|
|
|
|
//==== Placeholder for new feat bases on RHEL Edge
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-installation"]
|
|
|
|
|
=== Installation
|
|
|
|
|
This release includes integration with the greenboot health check framework. Greenboot assesses system health and automates a rollback to the last healthy state in the event of software trouble. You can add the optional greenboot RPM to your installation. For more information, read the xref:../microshift_running_apps/microshift-greenboot.adoc#microshirt-greenboot[Greenboot documentation].
|
|
|
|
|
//[id="microshift-4-14-installation"]
|
|
|
|
|
//=== Installation
|
|
|
|
|
|
|
|
|
|
//[id="microshift-4-13-new-feature-for-use-at-installation"]
|
|
|
|
|
//[id="microshift-4-14-new-feature-for-use-at-installation"]
|
|
|
|
|
//==== New feature for use during installation here
|
|
|
|
|
//can include a note about a change in base RHEL image
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-support"]
|
|
|
|
|
=== Support
|
|
|
|
|
//[id="microshift-4-14-support"]
|
|
|
|
|
//=== Support
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-sos-reports"]
|
|
|
|
|
==== {product-title} sos reports
|
|
|
|
|
With this release you can run an `sos` report to collect troubleshooting information about a host. The report generates a detailed report with data from all enabled plugins and different components and applications in a system.
|
|
|
|
|
|
|
|
|
|
For more information, see xref:../microshift_support/microshift-sos-report.adoc#about-microshift-sos-reports_microshift-sos-report[About MicroShift sos reports].
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-etcd"]
|
|
|
|
|
==== {product-title} etcd
|
|
|
|
|
|
|
|
|
|
With this release, {product-title} etcd is run as a separate process whose lifecycle is managed automatically by {product-title}. You can gather `journalctl` logs to observe and debug the etcd server logs.
|
|
|
|
|
|
|
|
|
|
For more information, see xref:../microshift_support/microshift-etcd.html#microshift-observe-debug-etcd-server_microshift-etcd[Observe and debug the MicroShift etcd server].
|
|
|
|
|
|
|
|
|
|
//[id="microshift-4-13-post-installation"]
|
|
|
|
|
//[id="microshift-4-14-post-installation"]
|
|
|
|
|
//=== Post-installation configuration
|
|
|
|
|
|
|
|
|
|
//[id="microshift-4-13-administrator-perspective"]
|
|
|
|
|
//[id="microshift-4-14-administrator-perspective"]
|
|
|
|
|
//==== Administrator Perspective
|
|
|
|
|
//admin perspectives go here
|
|
|
|
|
|
|
|
|
|
//[id="ocp-4-13-security"]
|
|
|
|
|
//[id="ocp-4-14-security"]
|
|
|
|
|
//=== Security and compliance
|
|
|
|
|
//
|
|
|
|
|
// This content will be added post-GA, as it is asynchronous content.
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-networking"]
|
|
|
|
|
=== Networking
|
|
|
|
|
//[id="microshift-4-14-networking"]
|
|
|
|
|
//=== Networking
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-load-balancer"]
|
|
|
|
|
==== Deploying network load balancers on {product-title}
|
|
|
|
|
//[id="microshift-4-14-load-balancer"]
|
|
|
|
|
//==== Deploying network load balancers on {product-title}
|
|
|
|
|
|
|
|
|
|
{product-title} now offers a built-in implementation of network load balancers. For more details, see xref:../microshift_networking/microshift-networking.adoc#microshift-deploying-a-load-balancer_microshift-networking[Deploying a TCP load balancer on a workload].
|
|
|
|
|
//[id="microshift-4-14-storage"]
|
|
|
|
|
//=== Storage
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-storage"]
|
|
|
|
|
=== Storage
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-lvms-system-requirements"]
|
|
|
|
|
==== LVMS system requirements
|
|
|
|
|
|
|
|
|
|
{product-title} configures LVMS dynamically based on the Volume Groups present. For more details, read the xref:../microshift_storage/microshift-storage-plugin-overview.adoc#lvms-volume-group-name_microshift-storage-plugin-overview[LVMS system requirements] section of this documentation.
|
|
|
|
|
//[id="microshift-4-14-lvms-system-requirements"]
|
|
|
|
|
//==== LVMS system requirements
|
|
|
|
|
|
|
|
|
|
//[id="microshift-4-13-deprecated-removed-features"]
|
|
|
|
|
//== Deprecated and removed features
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-bug-fixes"]
|
|
|
|
|
[id="microshift-4-14-bug-fixes"]
|
|
|
|
|
== Bug fixes
|
|
|
|
|
|
|
|
|
|
* Previously, {product-title} generated `kubeconfig` files using certificate authorities (CA) shared by all embedded components. With this update, the CAs and certificates are reconfigured to ensure the `kubeconfig` files are independent. (link:https://issues.redhat.com/browse/OCPBUGS-10223[*OCPBUGS#10223*])
|
|
|
|
|
|
|
|
|
|
* Previously, the `systemd-resolved` configuration was used by kubelet as an alternative DNS resolver, but the DNS Corefile configuration did not use the same `systemd-resolved` configuration. With this update, {product-title} uses the network name resolution provided by `systemd-resolved` for both kubelet and cluster DNS when the `systemd-resolved.service` is enabled. (link:https://issues.redhat.com/browse/OCPBUGS-6786[*OCPBUGS-6786*])
|
|
|
|
|
|
|
|
|
|
//etc
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-known-issues"]
|
|
|
|
|
[id="microshift-4-14-known-issues"]
|
|
|
|
|
== Known issues
|
|
|
|
|
|
|
|
|
|
* OVN-Kubernetes sets up an iptable chain in the network address translation (NAT) table to handle incoming traffic to the NodePort service. When the NodePort service is not reachable or the connection is refused, check the iptable rules on the host to make sure the relevant rules are properly inserted.
|
|
|
|
|
@@ -142,7 +115,7 @@ $ ip route
|
|
|
|
|
----
|
|
|
|
|
This routing rule matches the Kubernetes service IP address range and forwards the packet to the gateway bridge `br-ex`. You must enable `ip_forward` on the host. After the packet is forwarded to the OVS bridge `br-ex`, it is handled by OpenFlow rules in OVS. OpenFlow then steers the packet to the OVN network and eventually to the pod.
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-asynchronous-errata-updates"]
|
|
|
|
|
[id="microshift-4-14-asynchronous-errata-updates"]
|
|
|
|
|
== Asynchronous errata updates
|
|
|
|
|
|
|
|
|
|
Security, bug fix, and enhancement updates for {product-title} {product-version} are released as asynchronous errata through the Red Hat Network. All {product-title} {product-version} errata are https://access.redhat.com/downloads/content/290/[available on the Red Hat Customer Portal]. Read the https://access.redhat.com/support/policy/updates/openshift[{product-title} Life Cycle] for more information about asynchronous errata.
|
|
|
|
|
@@ -156,11 +129,13 @@ Red Hat Customer Portal user accounts must have systems registered and consuming
|
|
|
|
|
|
|
|
|
|
This section will continue to be updated over time to provide notes on enhancements and bug fixes for future asynchronous errata releases of {product-title} {ocp-version}. Versioned asynchronous releases, for example with the form {product-title} {ocp-version}.z, will be detailed in subsections. In addition, releases in which the errata text cannot fit in the space provided by the advisory will be detailed in subsections that follow.
|
|
|
|
|
|
|
|
|
|
[id="microshift-4-13-0-dp"]
|
|
|
|
|
=== RHSA-2023:1329 - {product-title} 4.13.0 bug fix and security update
|
|
|
|
|
[id="microshift-4-14-0-dp"]
|
|
|
|
|
=== RHSA-2023:
|
|
|
|
|
|
|
|
|
|
Issued: 2023-05-17
|
|
|
|
|
Issued:
|
|
|
|
|
|
|
|
|
|
{product-title} release 4.13.0 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2023:1329[RHSA-2023:1329] advisory. The images that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2023:1326[RHSA-2023:1326] advisory.
|
|
|
|
|
{product-title} release 4.14.0 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHSA-2023:xxxx[RHSA-2023:xxxx] advisory. The images that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2023:xxxx[RHSA-2023:xxxx] advisory.
|
|
|
|
|
|
|
|
|
|
For the `TopoLVM image`, see link:https://catalog.redhat.com/software/containers/lvms4/topolvm-rhel9/63972de3adcb55263891b983?container-tabs=dockerfile[lvms4/topolvm-rhel9].
|
|
|
|
|
For the `TopoLVM image`, see link:https://catalog.redhat.com/software/containers/lvms4/topolvm-rhel9/63972de3adcb55263891b983?container-tabs=dockerfile[lvms4/topolvm-rhel9].
|
|
|
|
|
|
|
|
|
|
//TODO update
|
“Shauna Diaz”