feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity

Merge pull request #15704 from travisn/ceph-19.2.2

Browse Source 
core: Set default ceph version to v19.2.2
This commit is contained in:
Travis Nielsen
2025-04-14 13:40:46 -06:00
committed by GitHub
parent 651080d66f f62e6d9cc2
commit c59eb9a3df
16 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/CRDs/Cluster/ceph-cluster-crd.md
+6 -6
View File
@@ -26,7 +26,7 @@ Settings can be specified at the global level to apply to the cluster as a whole
* `external`:
* `enable`: if `true`, the cluster will not be managed by Rook but via an external entity. This mode is intended to connect to an existing cluster. In this case, Rook will only consume the external cluster. However, Rook will be able to deploy various daemons in Kubernetes such as object gateways, mds and nfs if an image is provided and will refuse otherwise. If this setting is enabled **all** the other options will be ignored except `cephVersion.image` and `dataDirHostPath`. See [external cluster configuration](external-cluster/external-cluster.md). If `cephVersion.image` is left blank, Rook will refuse the creation of extra CRs like object, file and nfs.
* `cephVersion`: The version information for launching the ceph daemons.
* `image`: The image used for running the ceph daemons. For example, `quay.io/ceph/ceph:v19.2.1`. For more details read the [container images section](#ceph-container-images).
* `image`: The image used for running the ceph daemons. For example, `quay.io/ceph/ceph:v19.2.2`. For more details read the [container images section](#ceph-container-images).
For the latest ceph images, see the [Ceph DockerHub](https://hub.docker.com/r/ceph/ceph/tags/).
To ensure a consistent version of the image is running across all nodes in the cluster, it is recommended to use a very specific image version.
Tags also exist that would give the latest version, but they are only recommended for test environments. For example, the tag `v19` will be updated each time a new Squid build is released.
@@ -121,8 +121,8 @@ These are general purpose Ceph container with all necessary daemons and dependen
| -------------------- | --------------------------------------------------------- |
| vRELNUM | Latest release in this series (e.g., **v19** = Squid) |
| vRELNUM.Y | Latest stable release in this stable series (e.g., v19.2) |
| vRELNUM.Y.Z | A specific release (e.g., v19.2.1) |
| vRELNUM.Y.Z-YYYYMMDD | A specific build (e.g., v19.2.1-20250202) |
| vRELNUM.Y.Z | A specific release (e.g., v19.2.2) |
| vRELNUM.Y.Z-YYYYMMDD | A specific build (e.g., v19.2.2-20250409) |
A specific will contain a specific release of Ceph as well as security fixes from the Operating System.
@@ -435,7 +435,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
@@ -542,7 +542,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
@@ -672,7 +672,7 @@ kubectl -n rook-ceph get CephCluster -o yaml
deviceClasses:
- name: hdd
version:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
version: 16.2.6-0
conditions:
- lastHeartbeatTime: "2021-03-02T21:22:11Z"
Documentation/CRDs/Cluster/host-cluster.md
+3 -3
View File
@@ -22,7 +22,7 @@ metadata:
spec:
cephVersion:
# see the "Cluster Settings" section below for more details on which image of ceph to run
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
@@ -49,7 +49,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
@@ -101,7 +101,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
Documentation/CRDs/Cluster/pvc-cluster.md
+3 -3
View File
@@ -18,7 +18,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
@@ -72,7 +72,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: false
dashboard:
enabled: true
@@ -128,7 +128,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
Documentation/CRDs/Cluster/stretch-cluster.md
+1 -1
View File
@@ -34,7 +34,7 @@ spec:
- name: b
- name: c
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: true
# Either storageClassDeviceSets or the storage section can be specified for creating OSDs.
# This example uses all devices for simplicity.
Documentation/Upgrade/ceph-upgrade.md
+5 -5
View File
@@ -39,7 +39,7 @@ Official Ceph container images can be found on [Quay](https://quay.io/repository
These images are tagged in a few ways:
* The most explicit form of tags are full-ceph-version-and-build tags (e.g., `v19.2.1-20250202`).
* The most explicit form of tags are full-ceph-version-and-build tags (e.g., `v19.2.2-20250409`).
These tags are recommended for production clusters, as there is no possibility for the cluster to
be heterogeneous with respect to the version of Ceph running in containers.
* Ceph major version tags (e.g., `v19`) are useful for development and test clusters so that the
@@ -56,7 +56,7 @@ CephCluster CRD (`spec.cephVersion.image`).
```console
ROOK_CLUSTER_NAMESPACE=rook-ceph
NEW_CEPH_IMAGE='quay.io/ceph/ceph:v19.2.1-20250202'
NEW_CEPH_IMAGE='quay.io/ceph/ceph:v19.2.2-20250409'
kubectl -n $ROOK_CLUSTER_NAMESPACE patch CephCluster $ROOK_CLUSTER_NAMESPACE --type=merge -p "{\"spec\": {\"cephVersion\": {\"image\": \"$NEW_CEPH_IMAGE\"}}}"
```
@@ -68,7 +68,7 @@ employed by the new Rook operator release. Employing an outdated Ceph version wi
in unexpected behaviour.
```console
kubectl -n rook-ceph set image deploy/rook-ceph-tools rook-ceph-tools=quay.io/ceph/ceph:v19.2.1-20250202
kubectl -n rook-ceph set image deploy/rook-ceph-tools rook-ceph-tools=quay.io/ceph/ceph:v19.2.2-20250409
```
#### **3. Wait for the pod updates**
@@ -86,9 +86,9 @@ Confirm the upgrade is completed when the versions are all on the desired Ceph v
kubectl -n $ROOK_CLUSTER_NAMESPACE get deployment -l rook_cluster=$ROOK_CLUSTER_NAMESPACE -o jsonpath='{range .items[*]}{"ceph-version="}{.metadata.labels.ceph-version}{"\n"}{end}' | sort | uniq
This cluster is not yet finished:
ceph-version=v18.2.4-0
ceph-version=v19.2.1-0
ceph-version=v19.2.2-0
This cluster is finished:
ceph-version=v19.2.1-0
ceph-version=v19.2.2-0
```
#### **4. Verify cluster health**
deploy/charts/rook-ceph-cluster/values.yaml
+3 -3
View File
@@ -25,7 +25,7 @@ toolbox:
# -- Enable Ceph debugging pod deployment. See [toolbox](../Troubleshooting/ceph-toolbox.md)
enabled: false
# -- Toolbox image, defaults to the image used by the Ceph cluster
image: #quay.io/ceph/ceph:v19.2.1
image: #quay.io/ceph/ceph:v19.2.2
# -- Toolbox tolerations
tolerations: []
# -- Toolbox affinity
@@ -94,9 +94,9 @@ cephClusterSpec:
# v18 is Reef, v19 is Squid
# RECOMMENDATION: In production, use a specific version tag instead of the general v18 flag, which pulls the latest release and could result in different
# versions running within the cluster. See tags available at https://hub.docker.com/r/ceph/ceph/tags/.
# If you want to be more precise, you can always use a timestamp tag such as quay.io/ceph/ceph:v19.2.1-20250202
# If you want to be more precise, you can always use a timestamp tag such as quay.io/ceph/ceph:v19.2.2-20250409
# This tag might not contain a new Ceph version, just security fixes from the underlying operating system, which will reduce vulnerabilities
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
# Whether to allow unsupported versions of Ceph. Currently Reef and Squid are supported.
# Future versions such as Tentacle (v20) would require this to be set to `true`.
# Do not set to true in production.
deploy/examples/cluster-external-management.yaml
+1 -1
View File
@@ -20,4 +20,4 @@ spec:
dataDirHostPath: /var/lib/rook
# providing an image is required, if you want to create other CRs (rgw, mds, nfs)
cephVersion:
image: quay.io/ceph/ceph:v19.2.1 # Should match external cluster version
image: quay.io/ceph/ceph:v19.2.2 # Should match external cluster version
deploy/examples/cluster-on-local-pvc.yaml
+1 -1
View File
@@ -174,7 +174,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: false
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
deploy/examples/cluster-on-pvc.yaml
+1 -1
View File
@@ -34,7 +34,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: false
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
deploy/examples/cluster-stretched-aws.yaml
+1 -1
View File
@@ -45,7 +45,7 @@ spec:
mgr:
count: 2
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: true
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
deploy/examples/cluster-stretched.yaml
+1 -1
View File
@@ -39,7 +39,7 @@ spec:
mgr:
count: 2
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
allowUnsupported: true
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
deploy/examples/cluster.yaml
+2 -2
View File
@@ -19,9 +19,9 @@ spec:
# v18 is Reef, v19 is Squid
# RECOMMENDATION: In production, use a specific version tag instead of the general v19 flag, which pulls the latest release and could result in different
# versions running within the cluster. See tags available at https://hub.docker.com/r/ceph/ceph/tags/.
# If you want to be more precise, you can always use a timestamp tag such as quay.io/ceph/ceph:v19.2.1-20250202
# If you want to be more precise, you can always use a timestamp tag such as quay.io/ceph/ceph:v19.2.2-20250409
# This tag might not contain a new Ceph version, just security fixes from the underlying operating system, which will reduce vulnerabilities
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
# Whether to allow unsupported versions of Ceph. Currently Reef and Squid are supported.
# Future versions such as Tentacle (v20) would require this to be set to `true`.
# Do not set to true in production.
deploy/examples/images.txt
+1 -1
View File
@@ -1,6 +1,6 @@
docker.io/rook/ceph:master
gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v20240513-v0.1.0-35-gefb3255
quay.io/ceph/ceph:v19.2.1
quay.io/ceph/ceph:v19.2.2
quay.io/ceph/cosi:v0.1.2
quay.io/cephcsi/cephcsi:v3.14.0
quay.io/csiaddons/k8s-sidecar:v0.12.0
design/ceph/ceph-cluster-cleanup.md
+1 -1
View File
@@ -34,7 +34,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dataDirHostPath: /var/lib/rook
mon:
count: 3
images/ceph/Makefile
+1 -1
View File
@@ -16,7 +16,7 @@ include ../image.mk
# ====================================================================================
# Image Build Options
CEPH_VERSION ?= v19.2.1-20250202
CEPH_VERSION ?= v19.2.2-20250409
REGISTRY_NAME = quay.io
BASEIMAGE = $(REGISTRY_NAME)/ceph/ceph:$(CEPH_VERSION)
tests/manifests/test-cluster-on-pvc-encrypted.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ spec:
requests:
storage: 5Gi
cephVersion:
image: quay.io/ceph/ceph:v19.2.1
image: quay.io/ceph/ceph:v19.2.2
dashboard:
enabled: false
network: