From 6e4c1b3020d40305baa8fdcf6cdcf3d95ed952a0 Mon Sep 17 00:00:00 2001
From: Florent Poinsard VitessKeyspaceTemplateI
VitessKeyspaceTemplateImages specifies user-definable container images to -use for this keyspace.
+use for this keyspace. The images defined here by the user will override +those defined at the top-level in VitessCluster.spec.images +Note: this structure is a copy of VitessKeyspaceImages, once we have gotten +rid of MysqldImage and replaced it by MysqldImageNew (planned for v2.15), we +should be able to remove VitessKeyspaceTemplateImages entirely and just use +VitessKeyspaceImages instead as it contains exactly the same fields.
+vttablet
+
+string
+
+ |
+
+ Vttablet is the container image (including version tag) to use for Vitess Tablet instances. + |
+
+vtorc
+
+string
+
+ |
+
+ Vtorc is the container image (including version tag) to use for Vitess Orchestrator instances. + |
+
+vtbackup
+
+string
+
+ |
+
+ Vtbackup is the container image (including version tag) to use for Vitess Backup jobs. + |
+
mysqld
@@ -6003,6 +6041,17 @@ VitessKeyspaceTemplateI mysqld running alongside each tablet. |
|
+mysqldExporter
+
+string
+
+ |
+
+ MysqldExporter specifies the container image for mysqld-exporter. + |
+
VitessKeyspaceTemplateImages specifies user-definable container images to use for this keyspace. The images defined here by the user will override -those defined at the top-level in VitessCluster.spec.images
+those defined at the top-level in VitessCluster.spec.images. +While this field allows you to set a different set of Vitess version for +some components of Vitess than the version defined at the top level, it +is important to note that Vitess only ensure compatibility between one +version and the next and previous one. For instance: N is only compatible +with N+1 and N-1. Do be careful when specifying multiple versions across +your cluster so that they respect this compatibility rule.
Note: this structure is a copy of VitessKeyspaceImages, once we have gotten
rid of MysqldImage and replaced it by MysqldImageNew (planned for v2.15), we
should be able to remove VitessKeyspaceTemplateImages entirely and just use
diff --git a/pkg/apis/planetscale/v2/vitesskeyspace_types.go b/pkg/apis/planetscale/v2/vitesskeyspace_types.go
index 370e17c9..5f1558f9 100644
--- a/pkg/apis/planetscale/v2/vitesskeyspace_types.go
+++ b/pkg/apis/planetscale/v2/vitesskeyspace_types.go
@@ -189,7 +189,14 @@ type VitessKeyspaceTemplate struct {
// VitessKeyspaceTemplateImages specifies user-definable container images to
// use for this keyspace. The images defined here by the user will override
-// those defined at the top-level in VitessCluster.spec.images
+// those defined at the top-level in VitessCluster.spec.images.
+//
+// While this field allows you to set a different set of Vitess version for
+// some components of Vitess than the version defined at the top level, it
+// is important to note that Vitess only ensure compatibility between one
+// version and the next and previous one. For instance: N is only compatible
+// with N+1 and N-1. Do be careful when specifying multiple versions across
+// your cluster so that they respect this compatibility rule.
//
// Note: this structure is a copy of VitessKeyspaceImages, once we have gotten
// rid of MysqldImage and replaced it by MysqldImageNew (planned for v2.15), we
From 29c74a1a905e2a91bf46392d6e00b72b0437320e Mon Sep 17 00:00:00 2001
From: Florent Poinsard VitessKeyspaceTemplateImages specifies user-definable container images to
use for this keyspace. The images defined here by the user will override
those defined at the top-level in VitessCluster.spec.images. While this field allows you to set a different set of Vitess version for
-some components of Vitess than the version defined at the top level, it
-is important to note that Vitess only ensure compatibility between one
-version and the next and previous one. For instance: N is only compatible
+ While this field allows you to set a different Vitess version for some
+components than the version defined at the top level, it is important to
+note that Vitess only ensures compatibility between one version and the
+next and previous one. For instance: N is only guaranteed to be compatible
with N+1 and N-1. Do be careful when specifying multiple versions across
your cluster so that they respect this compatibility rule. Note: this structure is a copy of VitessKeyspaceImages, once we have gotten
diff --git a/pkg/apis/planetscale/v2/vitesskeyspace_types.go b/pkg/apis/planetscale/v2/vitesskeyspace_types.go
index 5f1558f9..1d8dbdd0 100644
--- a/pkg/apis/planetscale/v2/vitesskeyspace_types.go
+++ b/pkg/apis/planetscale/v2/vitesskeyspace_types.go
@@ -191,10 +191,10 @@ type VitessKeyspaceTemplate struct {
// use for this keyspace. The images defined here by the user will override
// those defined at the top-level in VitessCluster.spec.images.
//
-// While this field allows you to set a different set of Vitess version for
-// some components of Vitess than the version defined at the top level, it
-// is important to note that Vitess only ensure compatibility between one
-// version and the next and previous one. For instance: N is only compatible
+// While this field allows you to set a different Vitess version for some
+// components than the version defined at the top level, it is important to
+// note that Vitess only ensures compatibility between one version and the
+// next and previous one. For instance: N is only guaranteed to be compatible
// with N+1 and N-1. Do be careful when specifying multiple versions across
// your cluster so that they respect this compatibility rule.
//
VitessKeyspaceTemplateI