core: make Ceph Tentacle default version
This commit make ceph tentacle as a default version in cluster-test.yaml so that local and ci testing can be done and also updating cluster.yaml to mention v20(tentacle). Signed-off-by: subhamkrai <srai@redhat.com>
This commit is contained in:
1 parent
ae41dafb0b
commit
88fb58bf2b
2 files changed
+6
-6
No files matched your search
@@ -15,7 +15,7 @@ metadata:
|
||||
spec:
|
||||
dataDirHostPath: /var/lib/rook
|
||||
cephVersion:
|
||||
image: quay.io/ceph/ceph:v19
|
||||
image: quay.io/ceph/ceph:v20
|
||||
allowUnsupported: true
|
||||
mon:
|
||||
count: 1
|
||||
|
||||
@@ -16,14 +16,14 @@ metadata:
|
||||
spec:
|
||||
cephVersion:
|
||||
# The container image used to launch the Ceph daemon pods (mon, mgr, osd, mds, rgw).
|
||||
# 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
|
||||
# v18 is Reef, v19 is Squid, v20 is Tentacle
|
||||
# RECOMMENDATION: In production, use a specific version tag instead of the general v20 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.3-20250717
|
||||
# If you want to be more precise, you can always use a timestamp tag such as quay.io/ceph/ceph:v20.2.0-20251104
|
||||
# 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.3
|
||||
# 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`.
|
||||
# Whether to allow unsupported versions of Ceph. Currently Reef, Squid, and Tentacle are supported.
|
||||
# Future versions such as Umbrella (v21) would require this to be set to `true`.
|
||||
# Do not set to true in production.
|
||||
allowUnsupported: false
|
||||
# The path on the host where configuration files will be persisted. Must be specified. If there are multiple clusters, the directory must be unique for each cluster.
|
||||
|
||||
Reference in new issue
Block a user