forked from rook/rook
Illya Chekrygin
c27bfc3bb4
Remove empty try/catch (erroneous commit) Update Teardown documentation Update PendingReleaseNotes with Operator resource changes Signed-off-by: Illya Chekrygin <illya.chekrygin@gmail.com>
1.6 KiB
1.6 KiB
Major Themes
Action Required
Notable Features
- Ceph tools can be run from any rook pod.
- Output from stderr will be included in error messages returned from the
execof external tools - Rook-Operator no longer creates the resources CRD's or TPR's at the runtime. Instead, those resources are provisioned during deployment via
helmorkubectl.
Breaking Changes
Removal of the API service and rookctl tool
The REST API service has been removed. All cluster configuration is now accomplished through the CRDs or with the Ceph tools in the toolbox.
The tool rookctl has been removed from the toolbox pod. Cluster status and configuration can be queried and changed with the Ceph tools.
Here are some sample commands to help with your transition.
rookctl Command |
Replaced by | Description |
|---|---|---|
rookctl status |
ceph status |
Query the status of the storage components |
rookctl block |
See the Block storage and direct Block config | Create, configure, mount, or unmount a block image |
rookctl filesystem |
See the Filesystem and direct File config | Create, configure, mount, or unmount a file system |
rookctl object |
See the Object storage config | Create and configure object stores and object users |