Skip to content

Commit

Permalink
Merge pull request #9352 from rook/mergify/bp/release-1.8/pr-9343
Browse files Browse the repository at this point in the history
core: bump to ceph 16.2.7 (backport #9343)
  • Loading branch information
mergify[bot] committed Dec 8, 2021
2 parents f2fd2b7 + 87cca6f commit 3ceaaaa
Show file tree
Hide file tree
Showing 16 changed files with 30 additions and 30 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/rgw-multisite-test/action.yml
Expand Up @@ -5,7 +5,7 @@ inputs:
description: GITHUB_TOKEN from the calling workflow
required: true
ceph-image:
description: Ceph image to use for the workflow (e.g., quay.io/ceph/ceph:v16.2.5)
description: Ceph image to use for the workflow (e.g., quay.io/ceph/ceph:v16.2.7)
required: false

runs:
Expand Down
24 changes: 12 additions & 12 deletions Documentation/ceph-cluster-crd.md
Expand Up @@ -32,7 +32,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:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -60,7 +60,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:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -129,7 +129,7 @@ spec:
- name: c
cephVersion:
# Stretch cluster is supported in Ceph Pacific or newer.
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: true
# Either storageClassDeviceSets or the storage section can be specified for creating OSDs.
# This example uses all devices for simplicity.
Expand Down Expand Up @@ -167,7 +167,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). 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:v15.2.12` or `v16.2.6`. 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:v15.2.12` or `v16.2.7`. 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 `v15` will be updated each time a new Octopus build is released.
Expand Down Expand Up @@ -687,7 +687,7 @@ kubectl -n rook-ceph get CephCluster -o yaml
deviceClasses:
- name: hdd
version:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
version: 16.2.6-0
conditions:
- lastHeartbeatTime: "2021-03-02T21:22:11Z"
Expand Down Expand Up @@ -749,7 +749,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -781,7 +781,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -821,7 +821,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -868,7 +868,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -974,7 +974,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down Expand Up @@ -1020,7 +1020,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: false
dashboard:
enabled: true
Expand Down Expand Up @@ -1478,7 +1478,7 @@ spec:
enable: true
dataDirHostPath: /var/lib/rook
cephVersion:
image: quay.io/ceph/ceph:v16.2.6 # Should match external cluster version
image: quay.io/ceph/ceph:v16.2.7 # Should match external cluster version
```

### Deleting a CephCluster
Expand Down
4 changes: 2 additions & 2 deletions Documentation/ceph-upgrade.md
Expand Up @@ -458,7 +458,7 @@ Prior to August 2021, official images were on docker.io. While those images will

These images are tagged in a few ways:

* The most explicit form of tags are full-ceph-version-and-build tags (e.g., `v16.2.6-20210918`).
* The most explicit form of tags are full-ceph-version-and-build tags (e.g., `v16.2.7-20211208`).
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., `v16`) are useful for development and test clusters so that the
Expand All @@ -474,7 +474,7 @@ The majority of the upgrade will be handled by the Rook operator. Begin the upgr
Ceph image field in the cluster CRD (`spec.cephVersion.image`).

```sh
NEW_CEPH_IMAGE='quay.io/ceph/ceph:v16.2.6-20210918'
NEW_CEPH_IMAGE='quay.io/ceph/ceph:v16.2.7-20211208'
CLUSTER_NAME="$ROOK_CLUSTER_NAMESPACE" # change if your cluster name is not the Rook namespace
kubectl -n $ROOK_CLUSTER_NAMESPACE patch CephCluster $CLUSTER_NAME --type=merge -p "{\"spec\": {\"cephVersion\": {\"image\": \"$NEW_CEPH_IMAGE\"}}}"
```
Expand Down
2 changes: 1 addition & 1 deletion deploy/charts/rook-ceph-cluster/values.yaml
Expand Up @@ -48,7 +48,7 @@ cephClusterSpec:
# 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 quay.io/ceph/ceph:v15.2.11-20200419
# 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:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
# Whether to allow unsupported versions of Ceph. Currently `octopus` and `pacific` are supported.
# Future versions such as `pacific` would require this to be set to `true`.
# Do not set to true in production.
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/cluster-external-management.yaml
Expand Up @@ -19,4 +19,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:v16.2.6 # Should match external cluster version
image: quay.io/ceph/ceph:v16.2.7 # Should match external cluster version
2 changes: 1 addition & 1 deletion deploy/examples/cluster-on-local-pvc.yaml
Expand Up @@ -173,7 +173,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: false
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/cluster-on-pvc.yaml
Expand Up @@ -33,7 +33,7 @@ spec:
requests:
storage: 10Gi
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: false
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/cluster-stretched-aws.yaml
Expand Up @@ -45,7 +45,7 @@ spec:
count: 2
cephVersion:
# Stretch cluster support upstream is only available starting in Ceph Pacific
image: quay.io/ceph/ceph:v16.2.2
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: true
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/cluster-stretched.yaml
Expand Up @@ -39,7 +39,7 @@ spec:
count: 2
cephVersion:
# Stretch cluster support upstream is only available starting in Ceph Pacific
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: true
skipUpgradeChecks: false
continueUpgradeAfterChecksEvenIfNotHealthy: false
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/cluster-test.yaml
Expand Up @@ -28,7 +28,7 @@ metadata:
spec:
dataDirHostPath: /var/lib/rook
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
allowUnsupported: true
mon:
count: 1
Expand Down
4 changes: 2 additions & 2 deletions deploy/examples/cluster.yaml
Expand Up @@ -19,9 +19,9 @@ spec:
# v15 is octopus, and v16 is pacific.
# RECOMMENDATION: In production, use a specific version tag instead of the general v14 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 quay.io/ceph/ceph:v16.2.6-20210918
# If you want to be more precise, you can always use a timestamp tag such quay.io/ceph/ceph:v16.2.7-20211208
# 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:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
# Whether to allow unsupported versions of Ceph. Currently `octopus` and `pacific` are supported.
# Future versions such as `pacific` would require this to be set to `true`.
# Do not set to true in production.
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/images.txt
Expand Up @@ -3,7 +3,7 @@
k8s.gcr.io/sig-storage/csi-provisioner:v3.0.0
k8s.gcr.io/sig-storage/csi-resizer:v1.3.0
k8s.gcr.io/sig-storage/csi-snapshotter:v4.2.0
quay.io/ceph/ceph:v16.2.6
quay.io/ceph/ceph:v16.2.7
quay.io/cephcsi/cephcsi:v3.4.0
quay.io/csiaddons/volumereplication-operator:v0.1.0
rook/ceph:v1.8.0-beta.0
2 changes: 1 addition & 1 deletion deploy/olm/assemble/metadata-common.yaml
Expand Up @@ -240,7 +240,7 @@ metadata:
},
"spec": {
"cephVersion": {
"image": "quay.io/ceph/ceph:v16.2.6"
"image": "quay.io/ceph/ceph:v16.2.7"
},
"dataDirHostPath": "/var/lib/rook",
"mon": {
Expand Down
2 changes: 1 addition & 1 deletion design/ceph/ceph-cluster-cleanup.md
Expand Up @@ -34,7 +34,7 @@ metadata:
namespace: rook-ceph
spec:
cephVersion:
image: quay.io/ceph/ceph:v16.2.6
image: quay.io/ceph/ceph:v16.2.7
dataDirHostPath: /var/lib/rook
mon:
count: 3
Expand Down
4 changes: 2 additions & 2 deletions images/ceph/Makefile
Expand Up @@ -18,9 +18,9 @@ include ../image.mk
# Image Build Options

ifeq ($(GOARCH),amd64)
CEPH_VERSION = v16.2.6-20210918
CEPH_VERSION = v16.2.7-20211208
else
CEPH_VERSION = v16.2.6-20210918
CEPH_VERSION = v16.2.7-20211208
endif
REGISTRY_NAME = quay.io
BASEIMAGE = $(REGISTRY_NAME)/ceph/ceph-$(GOARCH):$(CEPH_VERSION)
Expand Down
2 changes: 1 addition & 1 deletion tests/framework/installer/ceph_installer.go
Expand Up @@ -45,7 +45,7 @@ const (
// test with the latest octopus build
octopusTestImage = "quay.io/ceph/ceph:v15"
// test with the latest pacific build
pacificTestImage = "quay.io/ceph/ceph:v16.2.6"
pacificTestImage = "quay.io/ceph/ceph:v16"
// test with the current development version of Pacific
pacificDevelTestImage = "quay.io/ceph/daemon-base:latest-pacific-devel"
octopusDevelTestImage = "quay.io/ceph/daemon-base:latest-octopus-devel"
Expand Down

0 comments on commit 3ceaaaa

Please sign in to comment.