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

build: set release version to v1.19.1

Browse Source 
For the patch release update the docs and examples to
v1.19.1

Signed-off-by: Michael Adam <obnox@samba.org>
This commit is contained in:
Michael Adam authored and Travis Nielsen committed 2026-02-05 13:31:51 -07:00
1 parent bf65ba5c91
commit a42feeaac3
11 files changed
+23 -23
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.0 https://github.com/rook/rook.git
$ git clone --single-branch --branch v1.19.1 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.0 https://github.com/rook/rook.git
$ git clone --single-branch --branch v1.19.1 https://github.com/rook/rook.git
cd rook/deploy/examples/monitoring
```
Documentation/Upgrade/rook-upgrade.md
+12 -12
View File
@@ -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.9` to
the version `v1.19.0`. This upgrade should work from any official patch release of Rook v1.18 to any
the version `v1.19.1`. 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.0 https://github.com/rook/rook.git
git clone --single-branch --depth=1 --branch v1.19.1 https://github.com/rook/rook.git
cd rook/deploy/examples
```
@@ -209,7 +209,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.0
kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.19.1
```
### **3. Update Ceph CSI Custom Images **
@@ -233,16 +233,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.0`, the Ceph cluster's core components are fully updated.
availability and `rook-version=v1.19.1`, 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.0
rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.19.0
rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.19.0
rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.19.0
rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.19.0
rook-ceph-mgr-a req/upd/avl: 1/1/1 rook-version=v1.19.1
rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.19.1
rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.19.1
rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.19.1
rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.19.1
rook-ceph-osd-1 req/upd/avl: 1/1/1 rook-version=1.18.9
rook-ceph-osd-2 req/upd/avl: 1/1/1 rook-version=1.18.9
```
@@ -254,13 +254,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.9
rook-version=v1.19.0
rook-version=v1.19.1
This cluster is finished:
rook-version=v1.19.0
rook-version=v1.19.1
```
### **5. Verify the updated cluster**
At this point, the Rook operator should be running version `rook/ceph:v1.19.0`.
At this point, the Rook operator should be running version `rook/ceph:v1.19.1`.
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.0
tag: v1.19.1
# -- 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.0
image: docker.io/rook/ceph:v1.19.1
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.0
docker.io/rook/ceph:v1.19.1
gcr.io/k8s-staging-sig-storage/objectstorage-sidecar:v20240513-v0.1.0-35-gefb3255
quay.io/ceph/ceph:v19.2.3
quay.io/ceph/cosi:v0.1.2
deploy/examples/operator-openshift.yaml
+1 -1
View File
@@ -691,7 +691,7 @@ spec:
serviceAccountName: rook-ceph-system
containers:
- name: rook-ceph-operator
image: docker.io/rook/ceph:v1.19.0
image: docker.io/rook/ceph:v1.19.1
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.0
image: docker.io/rook/ceph:v1.19.1
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.0
image: docker.io/rook/ceph:v1.19.1
# 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.0
image: docker.io/rook/ceph:v1.19.1
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.0
image: docker.io/rook/ceph:v1.19.1
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.0
image: docker.io/rook/ceph:v1.19.1
command:
- /bin/bash
- -c