Skip to content

v0.7.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@jbw976 jbw976 released this 21 Feb 22:20
· 9633 commits to master since this release
v0.7.0
66a0783
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Notable Features

  • The Cluster CRD can now be edited/updated to add and remove storage nodes. Note that only adding/removing entire nodes is currently supported, but adding individual disks/directories will also be supported soon.
  • The rook/rook image now uses the official Ceph packages instead of compiling from source. This ensures that Rook always ships the latest stable and supported Ceph version and reduces the developer burden for maintenance and building.
  • Resource limits are now supported for all pod types. You can constrain the CPU and memory usage for all Rook pods by setting resource limits in the Cluster CRD.
  • Monitoring is now done through the Ceph MGR service for Ceph storage.
  • The CRUSH root can be specified for pools with the crushRoot property, rather than always using the default root. Configuration of the CRUSH hierarchy is necessary with the ceph osd crush commands in the toolbox.
  • A full client API has been generated for all Kubernetes resource types defined in Rook. This allows you to programmatically interact with Rook deployments using golang.
  • The full list of resolved issues can be found in the 0.7 milestone page

Operator Settings

  • AGENT_TOLERATION: Toleration can be added to the Rook agent, such as to run on the master node.
  • FLEXVOLUME_DIR_PATH: Flex volume directory can be overridden on the Rook agent.

Breaking Changes

  • armhf build of Rook have been removed. Ceph is not supported or tested on armhf. arm64 support continues.

Cluster CRD

  • Removed the versionTag property. The container version to launch in all pods will be the same as the version of the operator container.
  • Added the cluster.rook.io finalizer. When a cluster is deleted, the operator will cleanup resources and remove the finalizer, which then allows K8s to delete the CRD.

Operator

  • Removed the ROOK_REPO_PREFIX env var. All containers will be launched with the same image as the operator

Deprecations

Assets 2