diff --git a/_topic_maps/_topic_map_ms.yml b/_topic_maps/_topic_map_ms.yml index a69c86fe7d..e4293c88d6 100644 --- a/_topic_maps/_topic_map_ms.yml +++ b/_topic_maps/_topic_map_ms.yml @@ -35,8 +35,8 @@ Name: Release notes Dir: microshift_release_notes Distros: microshift Topics: -- Name: MicroShift 4.13 release notes - File: microshift-4-13-release-notes +- Name: MicroShift 4.14 release notes + File: microshift-4-14-release-notes --- Name: Getting started Dir: microshift_getting_started diff --git a/modules/microshift-man-config-ovs-bridge.adoc b/_unused_topics/microshift-man-config-ovs-bridge.adoc similarity index 100% rename from modules/microshift-man-config-ovs-bridge.adoc rename to _unused_topics/microshift-man-config-ovs-bridge.adoc diff --git a/_unused_topics/microshift-nodeport-unreachable-workaround.adoc b/_unused_topics/microshift-nodeport-unreachable-workaround.adoc new file mode 100644 index 0000000000..4bef2a62fc --- /dev/null +++ b/_unused_topics/microshift-nodeport-unreachable-workaround.adoc @@ -0,0 +1,45 @@ +// Module included in the following assemblies: +// +// * module may be unused in 4.13 + +:_content-type: PROCEDURE +[id="microshift-nodeport-unreachable-workaround_{context}"] += Manually restarting the `ovnkube-master` pod to resume node port traffic + +After you install {product-title}, NodePort service traffic might stop. To troubleshoot this issue, manually restart the `ovnkube-master` pod in the `openshift-ovn-kubernetes` namespace. + +.Prerequisites + +* The OpenShift CLI (`oc`) is installed. +* A cluster installed on infrastructure configured with the Open Virtual Network (OVN)-Kubernetes network plugin. +* Access to the `kubeconfig` file. +* The KUBECONFIG environment variable is set. + +.Procedure + +Run the commands listed in each step that follows to restore the `NodePort` service traffic after you install{product-title}: + +. Find the name of the ovn-master pod that you want to restart by running the following command: ++ +[source, terminal] +---- +$ pod=$(oc get pods -n openshift-ovn-kubernetes | grep ovnkube-master | awk -F " " '{print $1}') +---- + +. Force a restart of the of the ovnkube-master pod by running the following command: ++ +[source, terminal] +---- +$ oc -n openshift-ovn-kubernetes delete pod $pod +---- + +. Optional: To confirm that the ovnkube-master pod restarted, run the following command: ++ +[source, terminal] +---- +$ oc get pods -n openshift-ovn-kubernetes +---- +If the pod restarted, the listing of the running pods shows a different ovnkube-master pod name and age consistent with the procedure you just completed. + +. Verify that the `NodePort` service can now be reached. + diff --git a/microshift_networking/microshift-networking.adoc b/microshift_networking/microshift-networking.adoc index 29d3bc1735..bcbd6749e1 100644 --- a/microshift_networking/microshift-networking.adoc +++ b/microshift_networking/microshift-networking.adoc @@ -27,8 +27,6 @@ include::modules/microshift-configuring-ovn.adoc[leveloffset=+1] include::modules/microshift-restart-ovnkube-master.adoc[leveloffset=+1] -//include::modules/microshift-man-config-ovs-bridge.adoc[leveloffset=+1] - include::modules/microshift-http-proxy.adoc[leveloffset=+1] include::modules/microshift-rpm-ostree-https.adoc[leveloffset=+1] @@ -42,3 +40,9 @@ include::modules/microshift-deploying-a-load-balancer.adoc[leveloffset=+1] include::modules/microshift-blocking-nodeport-access.adoc[leveloffset=+1] include::modules/microshift-mDNS.adoc[leveloffset=+1] + +[role="_additional-resources"] +[id="additional-resources_microshift-understanding-networking-settings"] +.Additional resources + +* xref:../microshift_release_notes/microshift-4-14-release-notes.adoc#microshift-4-14-known-issues[{product-title} {product-version} release notes --> Known issues] diff --git a/microshift_release_notes/microshift-4-13-release-notes.adoc b/microshift_release_notes/microshift-4-14-release-notes.adoc similarity index 54% rename from microshift_release_notes/microshift-4-13-release-notes.adoc rename to microshift_release_notes/microshift-4-14-release-notes.adoc index ca7c19074a..562fbc59ab 100644 --- a/microshift_release_notes/microshift-4-13-release-notes.adoc +++ b/microshift_release_notes/microshift-4-14-release-notes.adoc @@ -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]. \ No newline at end of file +For the `TopoLVM image`, see link:https://catalog.redhat.com/software/containers/lvms4/topolvm-rhel9/63972de3adcb55263891b983?container-tabs=dockerfile[lvms4/topolvm-rhel9]. + +//TODO update \ No newline at end of file diff --git a/modules/microshift-cni.adoc b/modules/microshift-cni.adoc index 50a1f03265..9fb3427552 100644 --- a/modules/microshift-cni.adoc +++ b/modules/microshift-cni.adoc @@ -69,8 +69,6 @@ Networking features available with {product-title} {product-version} include: * Kubernetes network policy * Dynamic node IP * Cluster network on specified host interface -* Secondary gateway interface -* Dual stack Networking features not available with {product-title} {product-version}: @@ -118,21 +116,3 @@ Bridge mappings allow provider network traffic to reach the physical network. Tr [id="microshift-primary-gateway-interface_{context}"] === Primary gateway interface You can specify the desired host interface name in the `ovn.yaml` config file as `gatewayInterface`. The specified interface is added in OVS bridge br-ex which acts as gateway bridge for the CNI network. - -[id="microshift-secondary-gateway-interface_{context}"] -=== Secondary gateway interface -You can set up one additional host interface for cluster ingress and egress in the `ovn.yaml` config file. The additional interface is added in a second OVS bridge `br-ex1`. Cluster pod traffic directed to the additional host subnet is routed automatically based on the destination IP through br-ex1. - -Either two or three OVS bridges are created based on the CNI configuration: - -Default deployment:: -* The `externalGatewayInterface` is not specified in the `ovn.yaml` config file. -* Two OVS bridges, `br-ex` and `br-int`, are created. - -Customized deployment:: -* The `externalGatewayInterface` is user-specified in the `ovn.yaml` config file. -* Three OVS bridges are created: `br-ex`, `br-ex1` and `br-int`. - -The br-ex bridge is created by `microshift-ovs-init.service` or manually. The br-ex bridge contains statically programmed openflow rules which distinguish traffic to and from the host network (underlay) and the OVN network (overlay). - -The `br-int` bridge is created by the `ovnkube-master` container. The `br-int` bridge contains dynamically programmed openflow rules which handle cluster network traffic. diff --git a/modules/microshift-configuring-ovn.adoc b/modules/microshift-configuring-ovn.adoc index c46eecf6fa..51ee910b49 100644 --- a/modules/microshift-configuring-ovn.adoc +++ b/modules/microshift-configuring-ovn.adoc @@ -31,11 +31,9 @@ $ cat /etc/microshift/ovn.yaml.default ovsInit: disableOVSInit: false gatewayInterface: "" <1> - externalGatewayInterface: "" <2> mtu: 1400 ---- <1> The default value is an empty string that means "not-specified." The CNI network plugin auto-detects to interface with the default route. -<2> The default value is an empty string that means "disabled." . To customize your configuration, use the following table that lists the valid values you can use: + @@ -61,12 +59,6 @@ mtu: 1400 |Ingress that is the API gateway |eth0 -|`ovsInit.externalGatewayInterface` -|Alpha -|eth1 -|Ingress routing external traffic to your services and pods inside the node -|eth1 - |mtu |uint32 |auto @@ -91,7 +83,6 @@ If you change the `mtu` configuration value in the `ovn.yaml` file, you must res ovsInit: disableOVSInit: true gatewayInterface: eth0 - externalGatewayInterface: eth1 mtu: 1300 ---- diff --git a/welcome/index.adoc b/welcome/index.adoc index 217009a859..9d8678a818 100644 --- a/welcome/index.adoc +++ b/welcome/index.adoc @@ -53,7 +53,7 @@ ifdef::microshift[] To navigate the {product-title} documentation, use the navigation bars and links. Start with xref:../microshift_getting_started/microshift-understanding.adoc#microshift-understanding[Understanding {product-title}] and xref:../microshift_install/microshift-install-rpm.adoc#microshift-install-rpm[Installing]. -Next, view the xref:../microshift_release_notes/microshift-4-13-release-notes.adoc#microshift-4-13-release-notes[release notes]. +Next, view the xref:../microshift_release_notes/microshift-4-14-release-notes.adoc#microshift-4-14-release-notes[release notes]. * For information about Red Hat Device Edge, read the link:https://access.redhat.com/documentation/en-us/red_hat_device_edge/4/html/overview/device-edge-overview[Red Hat Device Edge overview]. * For information about Red Hat Enterprise Linux for Edge, read link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_installing_and_managing_rhel_for_edge_images/index[RHEL for Edge documentation]. @@ -73,6 +73,7 @@ ifdef::openshift-online,openshift-aro[] Start with **xref:../architecture/architecture.adoc#architecture-overview-architecture[Architecture]**. endif::[] +//replace with GA announcement for 4.14 ifdef::microshift[] [IMPORTANT] ====