Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerThese are the release notes for the installer package bundle for Runtime Fabric on VMs / Bare Metal. In addition to these release notes, see the Anypoint Runtime Fabric release notes and the complete Anypoint Runtime Fabric documentation.
May 12, 2023
The container logging format changed from JSON (docker-specific) to CRI (cri-o, containerd, etc.).
Issue Resolution | ID |
---|---|
The new Runtime Fabric Installer version 2.0.1683838781-797f198 enables you to log in correctly into Ops center. |
W-13191265 |
May 5, 2023
This release contains bug fixes only.
Issue Resolution | ID |
---|---|
Latest installer is based on gravity 5.5.77, which switches from Docker to containerd as the container manager. |
W-12353489 |
Ops center now displays medium or long term data for memory related metrics. |
W-12549948 |
Performance issues no longer occur when operating appliance clusters with high utilization or many apps after they are upgraded. |
W-11781677, W-12353489 |
Known Issue | Workaround | ID |
---|---|---|
When you log into the Ops Center using the |
To access Ops Center, use the |
W-13191265 |
Log format changed starting with Runtime Fabric installer version 2.0.1682628878-0253858. The log output scrambles information and affects multiline logging. |
|
W-13504485 |
December 14, 2022
This release contains bug fixes only.
Issue Resolution | ID |
---|---|
Runtime Fabric appliance upgrades no longer fail due to a long running |
W-11585892 |
This release upgrades Helm3 to v3.10.0. |
W-11820302 |
The Telegraf monitoring app no longer issues false alerts for node uptime. |
W-11740287 |
Known Issue | Workaround | ID |
---|---|---|
Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications. |
W-11781677 |
August 29, 2022
This release includes fixes for security vulnerabilities.
Issue Resolution | ID |
---|---|
This release includes fixes for security vulnerabilities. |
W-11585892 |
Known Issue | Workaround | ID |
---|---|---|
Starting with release 2.0.1661808686-2ff0e92, you might experience performance issues operating appliance clusters with high utilization or many apps, after they are upgraded. Usually during node maintenance. After the nodes are brought back into operation, they might show signs of increased CPU usage and fail to start deployed applications. |
W-11781677 |
August 12, 2022
This release adds support for Ubuntu 20.04 and RHEL 8.6
Description | Issue |
---|---|
When starting an upgrade, the installer now performs an InfluxDB size check. |
W-10606099 |
The etcd.tick Kapacitor alert no longer re-appears if you delete it. |
W-10760515 |
The systemd Kapacitor task is now works as expected. |
W-10833331 |
The |
W-10946440 |
The Ops Center Individual Node Memory Usage graph now shows the correct legend. |
W-10961514 |
The RTF readiness probe no longer fails with a |
W-10647444 |
Description | Issue |
---|---|
Runtime Fabric might issue false alerts about uptime. |
W-10819071 |
January 19, 2022
Added support for RHEL/CentOS 8.4 using install scripts version 20220112-f8b0e44 or later.
Known Issue | Workaround | ID |
---|---|---|
For RHEL/CentOS 8.4, the install scripts disable the Network Mangager Cloud Setup ( |
If you’re upgrading your node operating systems from RHEL/CentOS 8.3 to 8.4, you must disable the cat > disable_nm_cloud.sh << 'EOF' #!/bin/bash function perform_os_specific_operations() { set +e if [[ "$ID_LIKE" == *"fedora"* ]] && [[ $VERSION_ID == 8.4 ]]; then echo "Disabling nm-cloud-setup service on RHEL 8.4" systemctl disable nm-cloud-setup.service nm-cloud-setup.timer systemctl stop nm-cloud-setup.service nm-cloud-setup.timer echo "Removing ip rule prio 30400 on RHEL 8.4" ip rule del prio 30400 if [[ -d "/etc/systemd/system/nm-cloud-setup.service.d" ]]; then rm -rf /etc/systemd/system/nm-cloud-setup.service.d fi echo "Restarting NetworkManager.service on RHEL 8.4" systemctl restart NetworkManager.service fi set -e } source /etc/os-release perform_os_specific_operations EOF sudo chmod +x ./disable_nm_cloud.sh sudo ./disable_nm_cloud.sh |
N/A |
May 3, 2021
This release includes the following fix and enhancement:
Added: Support for RHEL/CentOS 8.3
Fixed: Issue that caused the Ops Center UI metrics retention page to sometimes fail to load after reboot.
Mar 4, 2021
This release includes the following fix and enhancement:
Added: Improvement to inject Google’s metadata server’s host record in the Planet container when using Google Cloud Platform.
Fixed: Issue with stale alerts being shown in the output of the gravity status
utility.
This release includes the following fixes and enhancements:
Added: RHEL/CentOS 7.9 support.
Added: Improvements to the resiliency of the dns-app component during upgrades.
Fixed: Custom taints were not tolerated by logging and monitoring services.
Fixed: Upgrades with etcd may break watches in internal services.
This release includes the following fixes and enhancements:
Added: RHEL/CentOS 8.1 and 8.2 support.
Added: Improvements in reducing etcd load when querying system services during heavy usage.
Added: Improvements in debug reporting to include cluster configuration information.
Added: Checks to prevent cluster from entering an inconsistent state when executing a rollback.
Fixed: Issue with cluster status reporting healthy when few nodes are reported offline.
Updated: TLS config to use secure ciphers and TLSv1.2 for Kubernetes internal components.
This release includes the following fixes and enhancements:
Added: Validation for proxy settings configured in the appliance.
Added: Pre-upgrade validation to mitigate overlay network failures.
Added: Improvements in appliance status to display detailed alerts and warnings.
Added: Improvements that increase the resiliency with the appliance upgrade process.
Fixed: Upgrades with etcd were not applied on worker nodes in some cases.
Fixed: Issue with cluster network which could in some cases cause node-to-node communication to hang indefinitely.
Fixed: Issue with log forwarding causing increased CPU utilization.
This release includes the following fixes and enhancements:
Added: Patch for CVE-2020-8558.
Added: Automated pre-upgrade checks for validating cluster state before applying the upgrade.
Added: Ability to update auth servers in teleport node config.
Added: Resiliency improvements to the upgrade agent.
Added: RHEL/CentOS 8.0 support.
Added: Logging improvements and an additional command line option for following the plan progress during upgrade.
Fixed: InfluxDB continuous queries resulting in max series limit exhaustion.
Fixed: Cleaning up residual kube-dns resources when upgrading from older versions.
Fixed: Issue with etcd shutdown phase during upgrade.
This release includes the following fixes and enhancements:
Added: Patch for CVE-2020-13379.
Added: Pre-upgrade checks to ensure that the previous upgrade operation was not in progress.
Fixed: Kubernetes API server entering failed state during failover.
Fixed: Ops Center Monitoring tab displaying Dashboard not found
error.
Fixed: Disk space check executing for volumes that don’t have disk requirements specified.
Fixed: Upgrade failure when manually resumed on a node with an incomplete state.
This release includes the following fixes and enhancements:
Added: CentOS 7.8 support.
Added: Stability and performance improvements.
Fixed: Issue with restarting etcd due to large request size during an upgrade.
Fixed: Issue with RPC agent credentials not being rotated during an upgrade.
Fixed: Issue with pulling images on slow network environments.
Fixed: Security issues.
This release includes the following fixes and enhancements:
Added: RHEL 7.8 support.
Fixed: Issue with Influxdb consuming high CPU and Memory in some cases over time.
Fixed: Issue with Teleport nodes failing to join after expand operation.
Fixed: Issue with missed etcd events caused by a forced reboot.
Updated: kube-apiserver and kubelet to use Mozilla modern compatibility ciphers.
This release includes the following fixes and enhancements:
Added: Cleanup mechanism within the appliance to prevent leaking cgroups.
Added: Detection for issues with the overlay network.
Added: Improvements with appliance upgrades and detection to prevent unsupported upgrade paths.
Fixed: Support for copying lengthy commands from the web terminal in the Ops Center.
This release includes the following fixes and enhancements:
Fixed: Mitigated issues with Buster-based Docker containers in some environments by rolling back to stretch.
Fixed: Fixed issue with Teleport nodes failing to upload recorded sessions after upgrading from older clusters.
This release includes the following fixes and enhancements:
Fixed: Spurious error message from telegraf-node pod.
Fixed: Connectivity between nodes degraded after being restarted.
Fixed: A 500 internal error when accessing monitoring and authentication settings using Ops Center.
Added: Ability to configure a non-authenticating SMTP server to be used for sending alerts.
This release includes the following fixes and enhancements:
Fixed: In some cases, HTTP and Anypoint Monitoring proxy configuration was removed and had to be re-applied.
Fixed: Unused docker0
interface, which had the potential to cause conflicts with existing services in the 172.17.0.0
range, was removed.
This release includes the following fixes and enhancements:
Fixed: Upgrade fails when a directory which does not exist is listed in /etc/mtab
Added: Patch for CVE-2019-11253.
Updated: Kubernetes upgraded to v1.13.12
.
This release includes the following fixes and enhancements:
Fixed: Connectivity between nodes was degraded in some cases after upgrading etcd.
Added: Patch for CVE-2019-11251.
Updated: Kubernetes upgraded to v1.13.11
.
This release includes the following fixes and enhancements:
Added: Support for more than 3 controller nodes.
This release includes the following fixes and enhancements:
Added: Patch for CVE-2019-9512, CVE-2019-9514, CVE-2019-9512, CVE-2019-9514.
Added: Support for RHEL/CentOS 7.7
Updated: Kubernetes upgraded to v1.13.10
.
This release includes the following fixes and enhancements:
Added: Patch for CVE-2019-11247 and CVE-2019-11249.
Updated: Kubernetes upgraded to v1.13.9
.
Fixed: Permission error when managing monitoring resources via gravity resource
command.
This release includes the following fixes and enhancements:
Added: Support for running backup and restore jobs through OpsCenter.
Added: Patches to address security vulnerabilities.
Updated: Kubernetes upgraded to v1.14.2
.
Updated: kubedns
replaced with coredns
to align with upstream Kubernetes defaults.
Updated: The patch component versioning scheme is now based on the build time.
(Correction: Kubernetes was upgraded to v1.13.6
)
This release includes the following fixes and enhancements:
Fixed: Docker proxy to support authorization credentials with special characters.
This release includes the following fixes and enhancements:
Added: Patch for CVE-2019-1002100 and CVE-2019-1002101.
This release includes the following fixes and enhancements:
Added: Script to allow updating HTTP proxy configuration. (See scripts/
directory)
This release includes the following fixes and enhancements:
Added: Security patch to address CVE-2019-5736
This release includes the following fixes and enhancements:
Added: Support for RHEL/CentOS 7.6
This release includes the following fixes and enhancements:
Added: Patch for internal component used by Ops Center