You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 28, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: docs/enterprise-edition-example.md
+13-14Lines changed: 13 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Enterprise edition tutorial
2
-
This tutorial will explain how to create a mysqlcluster that runs the enterprise version of mysql.
2
+
This tutorial will explain how to create a MySQL cluster that runs the enterprise version of MySQL.
3
3
4
4
## Prerequisites
5
5
6
-
- The mysql-operator repository checked out locally.
7
-
- Access to a Docker registry that contains the enterprise version of mysql.
6
+
- The MySQL operator repository checked out locally.
7
+
- Access to a Docker registry that contains the enterprise version of MySQL.
8
8
9
9
## 01 - Create the Operator
10
10
You will need to create the following:
@@ -14,18 +14,17 @@ You will need to create the following:
14
14
3. The Operator
15
15
4. The Agent ServiceAccount & RoleBinding
16
16
17
-
The creation of these resources can be achieved by following the [introductory tutorial][1]; return here before creating a MySQL Cluster.
17
+
The creation of these resources can be achieved by following the [introductory tutorial][1]; return here before creating a MySQL cluster.
18
18
19
19
## 02 - Create a secret with registry credentials
20
-
To be able to pull the mysql enterprise edition from docker it is necessary to provide credentials, these credentials must be supplied in the form of a Kubernetes secret.
20
+
To be able to pull the MySQL Enterprise Edition from Docker it is necessary to provide credentials, these credentials must be supplied in the form of a Kubernetes secret.
21
21
22
-
- The name of the secret `myregistrykey` must match the name in the `imagepullsecrets` which we will specify in the cluster config in step 03.
23
-
- The secret must be created in the same namespace as the MySQL Cluster which we will make in step 03. It must also be in the same namespace as the RBAC permissions created in step 01.
24
-
- If you are pulling the mysql enterprise image from a different registry then the secret must contain the relevant credentials for that registry.
22
+
- Remember the name of the secret *myregistrykey* as this will need to be used in step 03 when creating the cluster.
23
+
- If you are pulling the MySQL Enterprise image from a different registry than the one in the example then the secret must contain the relevant credentials for that registry.
25
24
26
-
>For alternative ways to create Kubernetes secretes see their documentation on [creating secrets from docker configs](https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod) or [creating secrets manually](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config).
25
+
>For alternative ways to create Kubernetes secrets see their documentation on [creating secrets from Docker configs](https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod) or [creating secrets manually](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config).
27
26
28
-
Enter your credentials into the following command and execute it to create a Kubernetes secret that will enable pulling images from the Docker store. add the `-n` flag to specify a namespace if you do not want to use the default namespace.
27
+
Enter your credentials into the following command and execute it to create a Kubernetes secret that will enable pulling images from the Docker store. Add the `-n` flag to specify a namespace if you do not want to use the default namespace.
Finally, create your MySQL Cluster with the required specifications entered under `spec:`
38
37
39
-
- The mysqlServer field should be the path to a registry containing the enterprise edition of MySQL.
40
-
- The imagePullSecret: name: Should be the name of a Kubernetes secret in the same namespace that contains your credentials for the docker registry.
41
-
- The version to be used must be specified, without this, a default version is used which is **not** guaranteed to match an available image of MySQL Enterprise.
42
-
- The namespace of the cluster must match the namespace of the secret we created in step 02.
38
+
- The `repository:` field should be the path to a Docker registry containing the enterprise edition of MySQL. If this is ommited, the default is taken from the MySQL operator field `defaultMysqlServer:` which you can also specify.
39
+
- The `imagePullSecrets`: field allows you to specify a list of Kubernetes secret names. These secret(s) should contains your credentials for the Docker registry.
40
+
- The version to be used should be specified, without this, a default version is used which is **not** guaranteed to match an available image of MySQL Enterprise.
41
+
- The namespace of the cluster must match the namespace of the RBAC permissions created in step 01.
fs.StringVar(&s.KubeConfig, "kubeconfig", s.KubeConfig, "Path to Kubeconfig file with authorization and master location information.")
118
124
fs.StringVar(&s.Master, "master", s.Master, "The address of the Kubernetes API server (overrides any value in kubeconfig).")
119
125
fs.StringVar(&s.Namespace, "namespace", metav1.NamespaceAll, "The namespace for which the MySQL operator manages MySQL clusters. Defaults to all.")
126
+
fs.StringVar(&s.Images.DefaultMySQLServerImage, "mysql-server-image", mysqlServer, "The name of the default target for the 'mysql-server' image (can be overridden on a per-cluster basis). Defaults to: "+mysqlServer+".")
120
127
fs.StringVar(&s.Images.MySQLAgentImage, "mysql-agent-image", s.Images.MySQLAgentImage, "The name of the target 'mysql-agent' image. Defaults to: iad.ocir.io/oracle/mysql-agent.")
121
128
fs.DurationVar(&s.MinResyncPeriod.Duration, "min-resync-period", s.MinResyncPeriod.Duration, "The resync period in reflectors will be random between MinResyncPeriod and 2*MinResyncPeriod.")
0 commit comments