Bot releases are hidden (Show)
Published by travisn over 4 years ago
Rook v1.2.5 is a patch release limited in scope and focusing on bug fixes.
Published by travisn over 4 years ago
Rook v1.2.4 is a patch release limited in scope and focusing on bug fixes.
Published by travisn over 4 years ago
Rook v1.2.3 is a patch release limited in scope and focusing on bug fixes.
Published by travisn almost 5 years ago
Rook v1.2.2 is a patch release limited in scope and focusing on bug fixes.
Published by travisn almost 5 years ago
Rook v1.1.9 is a patch release limited in scope and focusing on bug fixes.
Published by leseb almost 5 years ago
Rook v1.2.1 is a patch release limited in scope and focusing on bug fixes.
ROOK_CEPH_MON_HOST
for OSDs (#4589, @leseb)Published by BlaineEXE almost 5 years ago
If you are running a previous Rook version, please see the corresponding storage provider upgrade guide:
DISCOVER_DAEMON_UDEV_BLACKLIST
is added through which the user can blacklist the devicesskipUpgradeChecks
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.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.Status.Phase
property has been introduced for Rook-Ceph CRDs. The current possible values of status are Processing
, Ready
and Failed
. If the operator is performing any task regarding a Ceph related CR, its status will be reflected as Processing
. The Status will be changed to Failed
if the operator fails at some task related to the CR and will change to Ready
once the Rook-Ceph operator finishes all the tasks related to the CR.ROOK_UNREACHABLE_NODE_TOLERATION_SECONDS
(5 seconds by default). Represents the time to wait until the node controller will move Rook pods to other nodes after detecting an unreachable node.devicePathFilter
to support device filtering with path names, e.g. /dev/disk/by-path/pci-.*-sas-.*
./run/ceph
.<dataDirHostPath>/log/<namespace>
, the same as other Ceph daemons.tuneSlowDeviceClass
.topology
setting has been removed from the CephCluster CR. To configure the OSD topology, node labels must be applied.Filestore
OSDs on disks is now deprecated. Filestore
is in sustaining mode in Ceph.
storeType
storage config setting is now ignored
Filestore
typeBluestore
typeFilestore
OSDs will remain as Filestore
OSDsPublished by travisn almost 5 years ago
Rook v1.1.8 is a patch release limited in scope and focusing on bug fixes.
Published by travisn almost 5 years ago
Rook v1.1.7 is a patch release limited in scope and focusing on bug fixes.
Published by travisn almost 5 years ago
Rook v1.1.6 is a patch release limited in scope and focusing on bug fixes. Note that the v1.1.5 release was skipped.
Published by travisn almost 5 years ago
Rook v1.1.4 is a patch release limited in scope and focusing on bug fixes. Note that release v1.1.3 was skipped.
removeOSDsIfOutAndSafeToRemove
(#4116, @rohgupta)Published by travisn about 5 years ago
Rook v1.1.2 is a patch release limited in scope and focusing on bug fixes.
ext4
on RBD device (#3971, @humblec)Published by travisn about 5 years ago
Rook v1.1.1 is a patch release limited in scope and focusing on bug fixes.
Published by BlaineEXE about 5 years ago
If you are running a previous Rook version, please see the corresponding storage provider upgrade guide:
apiVersion
ybcluster.yugabytedb.rook.io
custom resource to easily deploy a cluster of YugabyteDB Database. Checkout its user guide to get started with YugabyteDB.AGENT_TOLERATIONS
and DISCOVER_TOLERATIONS
. Each accept list of tolerations for agent and discover pods accordingly.root
user, however.NodeAffinity
can be applied to rook-ceph-agent DaemonSet
with AGENT_NODE_AFFINITY
environment variable.NodeAffinity
can be applied to rook-discover DaemonSet
with DISCOVER_AGENT_NODE_AFFINITY
environment variable.managePodBudgets
flag in the cluster CR. When this is enabled, drains on OSDs will be blocked by default and dynamically unblocked in a safe manner one failureDomain at a time. When a failure domain is draining, it will be marked as no out for a longer time than the default DOWN/OUT interval.disruptionManagement
section of the CephCluster CR. This can be enabled with the manageMachineDisruptionBudgets
flag in the cluster CR.deviceClass
property to enablespec.Mon.AllowMultiplePerNode
---is now active when a cluster is firstmgr
to enable Ceph manager modulesmetadataDevice
to be set per OSD device in the device specific config
section.deviceClass
to the per OSD device specific config
section for setting custom crush device class per OSD.--db-devices
with Ceph 14.2.1 and newer clusters to explicitly set metadataDevice
per OSD.metadataDevice
but that device is not used as a metadata device by Ceph.storageClassDeviceSets
named portable
:
true
, the OSDs will be allowed to move between nodes during failover. This requires a storage class that supports portability (e.g. aws-ebs
, but not the local storage provisioner).false
, the OSDs will be assigned to a node permanently. Rook will configure Ceph's CRUSH map to support the portability.Mon.PreferredCount
setting has been removed.imagePullSecrets
option added to helm-chartobject.yaml
, using allNodes
is not supported anymore, and a transition path has been implemented in the code to migrate automatically without user intervention.allNodes: true
, Rook will replace each DaemonSet with a deployment (one for one replacement) gradually. This operation will be triggered on an update or when a new version of the operator is deployed. Once complete, it is expected that you edit your object CR with kubectl -n rook-ceph edit cephobjectstore.ceph.rook.io/my-store
and set allNodes: false
and instances
with the current number of RGW instances.Published by travisn about 5 years ago
Rook v1.0.6 is a patch release limited in scope and focusing on bug fixes.
Published by travisn about 5 years ago
Rook v1.0.5 is a patch release limited in scope and focusing on bug fixes.
Published by travisn over 5 years ago
Rook v1.0.4 is a patch release limited in scope and focusing on bug fixes.
G
or Gi
) (#2922 #3391, @noahdesu)Published by travisn over 5 years ago
Rook v1.0.3 is a patch release limited in scope and focusing on bug fixes.
--ms-learn-addr-from-peer=false
argument for ceph-osd (@leseb)Published by travisn over 5 years ago
Rook v0.9.3 is a patch release limited in scope and focusing on bug fixes.
Published by travisn over 5 years ago
Rook v1.0.2 is a patch release limited in scope and focusing on bug fixes.