|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +//microshift_release_notes/microshift-4-19-release-notes.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: CONCEPT |
| 6 | +[id="microshift-4-19-new-features-and-enhancements_{context}"] |
| 7 | += New features and enhancements |
| 8 | + |
| 9 | +[role="_abstract"] |
| 10 | +This release adds improvements related to the following components and concepts. |
| 11 | + |
| 12 | +[id="microshift-4-19-rhel-image-mode_{context}"] |
| 13 | +== {op-system-base} image mode (Generally Available) |
| 14 | + |
| 15 | +Installing {microshift-short} by using a bootc container image is now generally available. Previously available as a Technology Preview feature, {op-system-image} is a deployment method that uses a container-native approach to build, deploy, and manage the operating system as a `rhel-bootc` container image. See xref:../microshift_install_bootc/microshift-about-rhel-image-mode.adoc#microshift-about-rhel-image-mode[Understanding image mode for RHEL with {microshift-short}] for more information. |
| 16 | + |
| 17 | +[id="microshift-4-19-ingress-controller-two-config_{context}"] |
| 18 | +== Control ingress for your use case with additional parameters |
| 19 | + |
| 20 | +With this release, the `ingress.certificate.Secret`,`ingress.clientTLS`, `ingress.routeAdmissionPolicy`, and `ingress.tlsSecurityProfile` parameters are added to the YAML configuration file for {microshift-short}. These parameters specify security settings for the ingress controller. For more information, see xref:../microshift_configuring/microshift-ingress-controller.adoc#microshift-ingress-controller[Using ingress control for a {microshift-short} node]. |
| 21 | + |
| 22 | +[id="microshift-4-19-tls-config_{context}"] |
| 23 | +== {microshift-short} control plane enhanced with TLS |
| 24 | + |
| 25 | +With this release, configurable transport layer security (TLS) protocols on internal control plane components are enabled to help prevent known insecure protocols, ciphers, or algorithms from accessing the applications you run on {microshift-short}. You use either the TLS 1.2 or TLS 1.3 with {microshift-short}. For more information, see xref:../microshift_configuring/microshift_auth_security/microshift-tls-config.adoc#microshift-tls-config[Configuring TLS security profiles]. |
| 26 | + |
| 27 | +[id="microshift-4-19-greenboot-updated_{context}"] |
| 28 | +== Check application health with the {microshift-short} healthcheck command |
| 29 | + |
| 30 | +With this release, you can use the `microshift healthcheck` command with various options to run a basic health check on your applications. For more information, see xref:../microshift_running_apps/microshift-greenboot-workload-health-checks.adoc#microshift-greenboot-workload-health-checks[Greenboot workload health checks]. |
| 31 | + |
| 32 | +[id="microshift-4-19-observability-metrics_{context}"] |
| 33 | +== Collecting metrics using the {microshift-short} Observability service |
| 34 | + |
| 35 | +With this release, you can configure the {microshift-short} Observability service to collect performance and usage metrics for monitoring resources. The following predefined configurations differ in the amount of data collected: |
| 36 | + |
| 37 | +* Small |
| 38 | +* Medium |
| 39 | +* Large (default) |
| 40 | + |
| 41 | +For more information, see xref:../microshift_running_apps/microshift-observability-service.adoc#microshift-observability-service[Using {microshift-short}] Observability. |
| 42 | + |
| 43 | +[id="microshift-4-19-telemetry_{context}"] |
| 44 | +== Telemetry now available |
| 45 | +With this release, {microshift-short} adds the Telemeter API. Lightweight attributes can be sent from a connected node to Red{nbsp}Hat to monitor the health of the node. To opt-out of Telemetry, see xref:../microshift_support/microshift-remote-node-monitoring.adoc#microshift-remote-node-monitoring[Remote health monitoring with a connected node]. |
0 commit comments