Rancher Release - v2.0.5


#1

Release v2.0.5

Versions

NOTE - Image Name Changes: Please note that as of v2.0.0, our images will be rancher/rancher and rancher/rancher-agent. If you are using v1.6, please continue to use rancher/server and rancher/agent.

  • rancher/rancher:v2.0.5
  • rancher/rancher-agent:v2.0.5

Rancher Server Tags

Rancher server has 2 different tags. For each major release tag, we will provide documentation for the specific version.

  • rancher/rancher:latest tag will be our latest development builds. These builds will have been validated through our CI automation framework. These releases are not meant for deployment in production.
  • rancher/rancher:stable tag will be our latest stable release builds. This tag is the version that we recommend for production.

Please do not use releases with a rc{n} suffix. These rc builds are meant for the Rancher team to test builds.

Latest - v2.0.5 - rancher/rancher:latest

Stable - v2.0.4 - rancher/rancher:stable

Upgrades and Rollbacks

Rancher supports both upgrade and rollback starting with v2.0.2. Please note the version you would like to upgrade or rollback to change the Rancher version.

Any upgrade after v2.0.3, when scaling up workloads, new pods will be created [#14136] - In order to update scheduling rules for workloads [#13527], a new field was added to all workloads on update, which will cause any pods in workloads from previous versions to re-create.

Note: When rolling back, we are expecting you to rollback to the state at the time of your upgrade. Any changes post upgrade would not be reflected. In the case of rolling back using a Rancher single-node install, you must specify the exact version you want to change the Rancher version to, rather than using the default :latest tag.

Note: If you had the helm stable catalog enabled in v2.0.0, we’ve updated the catalog to start pointing directly to the kubernetes helm repo instead of an internal repo. Please delete the custom catalog that is now showing up and re-enable the helm stable. [#13582]

Enhancements

  • Support for OpenLDAP [#13814] - openLDAP has been implemented as an authentication provider and can be selected as an option.
  • Support for FreeIPA [#13815] - FreeIPA has been implemented as an authentication provider and can be selected as an option.
  • Cordon [#13623] - Added the ability to cordon/uncordon nodes. When you update a node to cordon, no pods will be able to be scheduled on the node.
  • Azure AKS Enhancements [#14164] - Added ability to select a different resource group for AKS advanced networking options.
  • Rancher CLI - to support Infrastructure as Code (IaC), two new commands have been added to the rancher CLI.
    • rancher export - allows the export of a managed Kubernetes cluster as a YAML definition file.
    • rancher up - allows the import of a YAML file for cluster creation within Rancher

Known Major Issues

  • After upgrade, ingresses may have some issues with showing 503s or inability to target new workloads, the current workaround is to re-create the ingress [#13611]

Major Bug Fixes since v2.0.4

  • Fixed an issue where adding in nested groups for AD was causing slower login times by making an option to disable searching using nested groups. [#14364]
  • Fixed an issue where when standard users created clusters, they were unable to download keys for nodes [#14024]
  • Fixed an issue where you couldn’t update the name for registry, configmaps or secrets [#14094]
  • Fixed an issue where attempting to configure OpenStack as a cloud provider wasn’t working [#14197]
  • Fixed an issue where you were unable to use CLI to install a local helm chart [#14251]
  • Fixed an issue where it looks as if you can must change the password for users logged in as an external auth provider [#14162]

Rancher CLI Downloads


#2

#3

Important

Starting with v2.0.5, the default network selected when creating a Kubernetes cluster has changed from canal to flannel. If you require network policy enforcements (no inter-project network communication) between projects, please make sure you select the appropriate canal network option. Existing Kubernetes clusters are not affected by this change.


#4

Known Major Issues

  • OpenLDAP is not doing a service account bind before trying to look up the user to authenticate openLDAP, so only openLDAP servers that allow anonymous binds are able to authenticate [#12729, #14456]
  • Active Directory Users upgrading: If you are unable to login after upgrading from v2.0.2 to v2.0.3+, we have introduced looking up groups recursively to support nested groups in AD. In v2.0.6, we are turning off the recursive group search by default and you will be able to upgrade to that version.
  • During upgrade, if a cluster used OSes that do not have persistent directories (i.e. RancherOS, CoreOS, boot2docker), then their cluster will fail as kubelets wouldn’t have been able to be started due to missing certificates [#14454]

#5

Known Major Issues

  • Authenticating with Active Directory: With v2.0.5 and v2.0.6, you are required to add in the domain as part of the service account username. [#14708]