feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity
Files
31669e959dbd4d44fcbc52cfa9b3749db349de10
my-rook-config/PendingReleaseNotes.md
T
d-luu 9c755fac66 ceph: added priority classes to components 
Adds priority class support to Ceph components
  to influence scheduler's pod preemption

Signed-off-by: d-luu <david@davidluu.info>
2019-11-15 16:28:41 -06:00

2.7 KiB
Raw Blame History

Major Themes

Action Required

Notable Features

  • Added K8s 1.16 to the test matrix and removed K8s 1.11 from the test matrix.

Ceph

  • The job for detecting the Ceph version can be started with node affinity or tolerations according to the same settings in the Cluster CR as the mons.
  • A new CR property skipUpgradeChecks has been added, which allows you force an upgrade by skipping daemon checks. Use this at YOUR OWN RISK, only if you know what you're doing. To understand Rook's upgrade process of Ceph, read the upgrade doc.
  • Mon Quorum Disaster Recovery guide has been updated to work with the latest Rook and Ceph release.
  • A new CRD property PreservePoolsOnDelete has been added to Filesystem(fs) and Object Store(os) resources in order to increase protection against data loss. if it is set to true, associated pools won't be deleted when the main resource(fs/os) is deleted. Creating again the deleted fs/os with the same name will reuse the preserved pools.
  • OSDs:
    • Ceph OSD's admin socket is now placed under Ceph's default system location /run/ceph.
    • The on-host log directory for OSDs was set incorrectly to <dataDirHostPath>/<namespace>/log; fix this to be <dataDirHostPath>/log/<namespace>, the same as other daemons.
    • Use the mon configuration database for directory-based OSDs, and do not generate a config
  • A new ceph-crashcollector controller has been added, that new pod will run on any node where a Ceph pod is running. Read more about this in the doc
  • PriorityClassNames can now be added to the Rook/Ceph components to influence the scheduler's pod preemption.

EdgeFS

YugabyteDB

Breaking Changes

Ceph

  • The topology setting has been removed from the CephCluster CR. To configure the OSD topology, node labels must be applied. See the OSD topology topic. This setting only affects OSDs when they are first created, thus OSDs will not be impacted during upgrade. The topology settings only apply to bluestore OSDs on raw devices. The topology labels are not applied to directory-based OSDs.

Known Issues

Deprecations

View Git Blame Copy Permalink