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

build: set the release version to v1.19.4

Browse Source 
For the patch release update the docs and images to
v1.19.4

Signed-off-by: Michael Adam <obnox@samba.org>
This commit is contained in:
Michael Adam committed 2026-04-14 20:46:30 +02:00
1 parent a1939fd093
commit 4e1d7b7879
11 files changed
+26 -26
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

Documentation/Getting-Started/quickstart.md
+1 -1
View File
@@ -36,7 +36,7 @@ To configure the Ceph storage cluster, at least one of these local storage optio
A simple Rook cluster is created for Kubernetes with the following `kubectl` commands and [example manifests](https://github.com/rook/rook/blob/master/deploy/examples).
```console
$ git clone --single-branch --branch v1.19.3 https://github.com/rook/rook.git
$ git clone --single-branch --branch v1.19.4 https://github.com/rook/rook.git
cd rook/deploy/examples
kubectl create -f crds.yaml -f common.yaml -f csi-operator.yaml -f operator.yaml
kubectl create -f cluster.yaml
Documentation/Storage-Configuration/Monitoring/ceph-monitoring.md
+1 -1
View File
@@ -48,7 +48,7 @@ There are two sources for metrics collection:
From the root of your locally cloned Rook repo, go the monitoring directory:
```console
$ git clone --single-branch --branch v1.19.3 https://github.com/rook/rook.git
$ git clone --single-branch --branch v1.19.4 https://github.com/rook/rook.git
cd rook/deploy/examples/monitoring
```
Documentation/Upgrade/rook-upgrade.md
+15 -15
View File
@@ -92,11 +92,11 @@ With this upgrade guide, there are a few notes to consider:
Unless otherwise noted due to extenuating requirements, upgrades from one patch release of Rook to
another are as simple as updating the common resources and the image of the Rook operator. For
example, when Rook v1.19.3 is released, the process of updating from v1.19.0 is as simple as running
example, when Rook v1.19.4 is released, the process of updating from v1.19.0 is as simple as running
the following:
```console
git clone --single-branch --depth=1 --branch v1.19.3 https://github.com/rook/rook.git
git clone --single-branch --depth=1 --branch v1.19.4 https://github.com/rook/rook.git
cd rook/deploy/examples
```
@@ -108,7 +108,7 @@ Then, apply the latest changes from v1.19, and update the Rook Operator image.
```console
kubectl apply -f common.yaml -f crds.yaml -f csi-operator.yaml
kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.19.3
kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.19.4
```
As exemplified above, it is a good practice to update Rook common resources from the example
@@ -143,7 +143,7 @@ In order to successfully upgrade a Rook cluster, the following prerequisites mus
## Rook Operator Upgrade
The examples given in this guide upgrade a live Rook cluster running `1.18.10` to
the version `v1.19.3`. This upgrade should work from any official patch release of Rook v1.18 to any
the version `v1.19.4`. This upgrade should work from any official patch release of Rook v1.18 to any
official patch release of v1.19.
Let's get started!
@@ -170,7 +170,7 @@ by the Operator. Also update the Custom Resource Definitions (CRDs).
Get the latest common resources manifests that contain the latest changes.
```console
git clone --single-branch --depth=1 --branch v1.19.3 https://github.com/rook/rook.git
git clone --single-branch --depth=1 --branch v1.19.4 https://github.com/rook/rook.git
cd rook/deploy/examples
```
@@ -212,7 +212,7 @@ The largest portion of the upgrade is triggered when the operator's image is upd
When the operator is updated, it will proceed to update all of the Ceph daemons.
```console
kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.19.3
kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.19.4
```
### **3. Update Ceph CSI Custom Images **
@@ -236,16 +236,16 @@ watch --exec kubectl -n $ROOK_CLUSTER_NAMESPACE get deployments -l rook_cluster=
```
As an example, this cluster is midway through updating the OSDs. When all deployments report `1/1/1`
availability and `rook-version=v1.19.3`, the Ceph cluster's core components are fully updated.
availability and `rook-version=v1.19.4`, the Ceph cluster's core components are fully updated.
```console
Every 2.0s: kubectl -n rook-ceph get deployment -o j...
rook-ceph-mgr-a req/upd/avl: 1/1/1 rook-version=v1.19.3
rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.19.3
rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.19.3
rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.19.3
rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.19.3
rook-ceph-mgr-a req/upd/avl: 1/1/1 rook-version=v1.19.4
rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.19.4
rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.19.4
rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.19.4
rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.19.4
rook-ceph-osd-1 req/upd/avl: 1/1/1 rook-version=1.18.10
rook-ceph-osd-2 req/upd/avl: 1/1/1 rook-version=1.18.10
```
@@ -257,13 +257,13 @@ An easy check to see if the upgrade is totally finished is to check that there i
# kubectl -n $ROOK_CLUSTER_NAMESPACE get deployment -l rook_cluster=$ROOK_CLUSTER_NAMESPACE -o jsonpath='{range .items[*]}{"rook-version="}{.metadata.labels.rook-version}{"\n"}{end}' | sort | uniq
This cluster is not yet finished:
rook-version=1.18.10
rook-version=v1.19.3
rook-version=v1.19.4
This cluster is finished:
rook-version=v1.19.3
rook-version=v1.19.4
```
### **5. Verify the updated cluster**
At this point, the Rook operator should be running version `rook/ceph:v1.19.3`.
At this point, the Rook operator should be running version `rook/ceph:v1.19.4`.
Verify the CephCluster health using the [health verification doc](health-verification.md).
deploy/charts/rook-ceph/values.yaml
+1 -1
View File
@@ -7,7 +7,7 @@ image:
repository: docker.io/rook/ceph
# -- Image tag
# @default -- `master`
tag: v1.19.3
tag: v1.19.4
# -- Image pull policy
pullPolicy: IfNotPresent
deploy/examples/direct-mount.yaml
+1 -1
View File
@@ -19,7 +19,7 @@ spec:
serviceAccountName: rook-ceph-default
containers:
- name: rook-direct-mount
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
command: ["/bin/bash"]
args: ["-m", "-c", "/usr/local/bin/toolbox.sh"]
imagePullPolicy: IfNotPresent
deploy/examples/images.txt
+1 -1
View File
@@ -1,4 +1,4 @@
docker.io/rook/ceph:v1.19.3
docker.io/rook/ceph:v1.19.4
gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v0.2.2
quay.io/ceph/ceph:v20.2.1
quay.io/ceph/cosi:v0.1.4
deploy/examples/operator-openshift.yaml
+1 -1
View File
@@ -693,7 +693,7 @@ spec:
serviceAccountName: rook-ceph-system
containers:
- name: rook-ceph-operator
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
args: ["ceph", "operator"]
securityContext:
runAsNonRoot: true
deploy/examples/operator.yaml
+1 -1
View File
@@ -615,7 +615,7 @@ spec:
serviceAccountName: rook-ceph-system
containers:
- name: rook-ceph-operator
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
args: ["ceph", "operator"]
securityContext:
runAsNonRoot: true
deploy/examples/osd-purge.yaml
+1 -1
View File
@@ -28,7 +28,7 @@ spec:
serviceAccountName: rook-ceph-purge-osd
containers:
- name: osd-removal
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
# TODO: Insert the OSD ID in the last parameter that is to be removed
# The OSD IDs are a comma-separated list. For example: "0" or "0,2".
# If you want to preserve the OSD PVCs, set `--preserve-pvc true`.
deploy/examples/toolbox-job.yaml
+2 -2
View File
@@ -10,7 +10,7 @@ spec:
spec:
initContainers:
- name: config-init
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
command: ["/usr/local/bin/toolbox.sh"]
args: ["--skip-watch"]
imagePullPolicy: IfNotPresent
@@ -32,7 +32,7 @@ spec:
readOnly: true
containers:
- name: script
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
volumeMounts:
- mountPath: /etc/ceph
name: ceph-config
deploy/examples/toolbox-operator-image.yaml
+1 -1
View File
@@ -25,7 +25,7 @@ spec:
serviceAccountName: rook-ceph-default
containers:
- name: rook-ceph-tools-operator-image
image: docker.io/rook/ceph:v1.19.3
image: docker.io/rook/ceph:v1.19.4
command:
- /bin/bash
- -c