Not able to deploy mysql 5.7 after values.yaml edit

MySQL & MariaDB Percona Operator for MySQL
,
1

Hi, I am using helm charts to deploy the cluster. We are just trying out the stack. so after editing the values.yaml

helm versisons

Screenshot 2021-03-08 120340
Screenshot 2021-03-08 1203401080×53 5.39 KB

Blockquote
pxc:
size: 3
image:
repository: percona/percona-xtradb-cluster
tag: 5.7.32-31.47
Blockquote

helm install dev .

kubectl describe pxc

Blockquote
Pxc:
Affinity:
Anti Affinity Topology Key: kubernetes.io/hostname
Auto Recovery: true
Grace Period: 600
Image: percona/percona-xtradb-cluster:8.0.21-12.1
Image Pull Policy: Always
Liveness Delay Sec: 300
Pod Disruption Budget:
Max Unavailable: 1
Pod Security Context:
Fs Group: 1001
Supplemental Groups:
1001
Readiness Delay Sec: 15
Resources:
Limits:
Requests:
Cpu: 600m
Memory: 1G
Service Account Name: default
Size: 3
Ssl Internal Secret Name: dev-pxc-db-ssl-internal
Ssl Secret Name: dev-pxc-db-ssl
Vault Secret Name: dev-pxc-db-vault
Volume Spec:
Empty Dir:
Secrets Name: dev-pxc-db
Ssl Internal Secret Name: dev-pxc-db-ssl-internal
Ssl Secret Name: dev-pxc-db-ssl
Update Strategy: SmartUpdate
Upgrade Options:
Apply: recommended
Schedule: 0 4 * * *
Version Service Endpoint: https://check.percona.com
Vault Secret Name: dev-pxc-db-vault

Blockquote

so the workaround was to patch the cluster using this

Blockquote
kubectl patch pxc dev-pxc-db --type=merge --patch ‘{
“spec”: {
“crVersion”:“1.7.0”,
“pxc”:{ “image”: “percona/percona-xtradb-cluster:5.7.32-31.47” },
“proxysql”: { “image”: “percona/percona-xtradb-cluster-operator:1.7.0-proxysql” },
“haproxy”: { “image”: “percona/percona-xtradb-cluster-operator:1.7.0-haproxy” },
“backup”: { “image”: “percona/percona-xtradb-cluster-operator:1.7.0-pxc5.7-backup” },
“logcollector”: { “image”: “percona/percona-xtradb-cluster-operator:1.7.0-logcollector” },
“pmm”: { “image”: “percona/pmm-client:2.12.0” }
}}’

Blockquote

Is there no way to skip the patching to get mysql 5.7 ?

1 Like
2

Hello @favas ,

thank you for submitting this! As stated in our documentation here, our smart update will upgrade newly provisioned clusters to the latest possible version, which is 8.0.

There are couple of ways to solve this:

  1. You can disable Smart Update by adding updateStrategy: Never into the values.yaml file.

  2. You can set the exact PXC version into the apply flag in values.yaml:

     pxc:
   size: 3

 upgradeOptions:
   apply: 5.7.32-31.47

Please let me know if it helps.

2 Likes