Files
my-rook-config/PendingReleaseNotes.md
T
Blaine Gardner 78d4719125 ceph: no longer create fallback osd
Rook's behavior should not be to create a default OSD in dataDirHostPath
when no devices are present on a node. Any preexisting fallback osd
should be kept as long as no dirs or disks have been specified to keep
the legacy behavior for those clusters running with these osds in place.
The legacy deletion behavior is also kept, removing the osd as soon as
any dir or device is specified other than the dataDirHostPath dir.

Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
2019-02-01 09:41:32 -07:00

1.1 KiB

Major Themes

Action Required

Notable Features

Minio Object Stores:

- Now have an additional label named `objectstore` with the name of the Object Store, to allow better selection for Services.
- Use `Readiness` and `Liveness` probes.
- Updated automatically on Object Store CRD changes.

Ceph

  • A CephNFS CRD will start NFS daemon(s) for exporting CephFS volumes or RGW buckets. See the NFS documentation.
  • Selinux labeling for mounts can now be toggled with the ROOK_ENABLE_SELINUX_RELABELING environment variable.
  • Recursive chown for mounts can now be toggled with the ROOK_ENABLE_FSGROUP environment variable.
  • Added the dashboard port configuration setting.
  • Added the dashboard ssl configuration setting.

Breaking Changes

  • Rook no longer supports Kubernetes 1.8 and 1.9.

Ceph

  • Rook will no longer create a directory-based osd in the dataDirHostPath if no directories or devices are specified or if there are no disks on the host.

Known Issues

Deprecations