feedc0de/my-rook-config
1
0 Fork 0
forked from rook/rook
Code Pull Requests Activity
Files
d65713cc157e1045e8ca61d25073dc38a6822632
my-rook-config/PendingReleaseNotes.md
T
Blaine Gardner ca71b7a311 Ceph mgr: Set up config in init container 
Progress toward issue #2003.
Includes design from design doc PR #1578

Use init containers to create configuration for Ceph mgrs. There is only
1 init container in this design:
 1. Using the Rook image, call the Rook binary to create Ceph config
files shared with the mgr daemgr container.

Once this init is run, the main mgr daemgr is run. Leaving room to use
the Ceph-versioned image in the future, call `ceph-mgr --foreground ...`
to run the Ceph mgr.

Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
2018-09-21 13:11:08 -06:00

2.4 KiB
Raw Blame History

Major Themes

Action Required

Notable Features

  • The fsType default for StorageClass examples are now using XFS to bring it in line with Ceph recommendations.
  • Ceph is updated from Luminous 12.2.5 to 12.2.7.
  • Ceph OSDs will be automatically updated by the operator when there is a change to the operator version or when the OSD configuration changes. See the OSD upgrade notes.
  • Rook Ceph block storage provisioner can now correctly create erasure coded block images. See Advanced Example: Erasure Coded Block Storage for an example usage.
  • Network File System (NFS) is now supported by Rook with a new operator to deploy and manage this widely used server. NFS servers can be automatically deployed by creating an instance of the new nfsservers.nfs.rook.io custom resource. See the NFS server user guide to get started with NFS.
  • The minimum version of Kubernetes supported by Rook changed from 1.7 to 1.8.
  • reclaimPolicy parameter of StorageClass definition is now supported.

Breaking Changes

  • Ceph mons are named consistently with other daemons with the letters a, b, c, etc.

  • Ceph mons are now created with Deployments instead of ReplicaSets to improve the upgrade implementation.

  • Ceph mon and mgr container names in pods have changed with the refactor to initialize the mon daemon environment via pod InitContainers and run the Ceph daemons directly from the container entrypoint.

  • The Rook container images are no longer published to quay.io, they are published only to Docker Hub. All manifests have referenced Docker Hub for multiple releases now, so we do not expect any directly affected users from this change.

  • Rook no longer supports kubernetes 1.7. Users running Kubernetes 1.7 on their clusters are recommended to upgrade to Kubernetes 1.8 or higher. If you are using kubeadm, you can follow this guide to from Kubernetes 1.7 to 1.8. If you are using kops or kubespray for managing your Kubernetes cluster, just follow the respective projects' upgrade guide.

Known Issues

Deprecations

View Git Blame Copy Permalink