airgapped-docs-0.1.49

Rancher Government Airgapped Docs

rancher-2.7.11

Install Rancher Server to manage Kubernetes clusters across providers

Full upstream release notes: https://github.com/rancher/rancher/releases/tag/v2.7.11

It is important to review the Install/Upgrade Notes below before upgrading to any Rancher version.

Warning: You should avoid upgrading from Rancher v2.7.11 to Rancher v2.8.0, v2.8.1, or v2.8.2. Rancher v2.7.11 contains critical fixes not present in Rancher v2.8.0, v2.8.1, or v2.8.2. Rancher offers several actively-developed minor release lines, and Rancher v2.7.11 was released chronologically after Rancher v2.8.2. The critical fixes present in Rancher v2.7.11 will be included in the next v2.8.x release.
Rancher v2.7.11 adds support for Kubernetes v1.27 and addresses several bugs and issues.

Features and Enhancements

• Rancher v2.7 now supports Kubernetes v1.27. See rancher/rancher#44098.

Major Bug Fixes

• Improved reliability of machine pool scaling for node driver provisioned RKE2/K3s clusters. See rancher/rancher#44198.
• Fixed a bug where, if V1 Monitoring is installed, requests to /v1/endpoints would throw a 500 error and caused the cluster to enter an Updating state. See rancher/rancher#44371.
• Fixed a bug which caused fleet-agent to panic and become stuck in an Updating state. See rancher/rancher#44175.
• Fixed a bug where the local Rancher cluster became stuck in a panic loop after deleting downstream clusters. See rancher/rancher#44299.

Rancher Behavior Changes

• Rancher no longer supports the Amazon Web Services (AWS) in-tree cloud provider for RKE clusters. This includes both RKE1 and RKE2. Upstream Kubernetes removed the in-tree AWS provider in Kubernetes v1.27. You should instead use the out-of-tree AWS cloud provider for any Rancher-managed clusters running Kubernetes v1.27 or later. This includes both RKE1 and RKE2. See the following issues:
  • RKE1 support: rancher/rancher#44144.
  • RKE2 support: rancher/rancher#44145.

Known Issues

• When you create a new namespace in a project that has Container Default Resource Limits defined, a limit range is not made for that namespace. Also, when creating a new kubeconfig file, a new token is not created. See rancher/rancher#44406.
• When you run a CIS v1.7 scan on RKE and RKE2 clusters that are on Kubernetes v1.27, some rancher/rancher#44106 (comment). The expected failures affect hardened RKE clusters, and both permissive and hardened RKE2 clusters. K3s clusters are not affected. See rancher/rancher#44106.

airgapped-docs-0.1.48

Rancher Government Airgapped Docs

rancher-2.8.2

Install Rancher Server to manage Kubernetes clusters across providers

rancher-2.7.10

Install Rancher Server to manage Kubernetes clusters across providers

rancher-2.6.14

Install Rancher Server to manage Kubernetes clusters across providers

rancher-2.8.1

Install Rancher Server to manage Kubernetes clusters across providers

rancher-2.8.0

Install Rancher Server to manage Kubernetes clusters across providers

stigatron-0.2.5

Rancher Government Stigatron Extension

airgapped-docs-0.1.47

Rancher Government Airgapped Docs