I have encountered some problems using the pxc operator in k8s v1.20.4
Description
Environment
Attachments
Smart Checklist
Activity
Slava Sarzhan April 20, 2022 at 2:34 PM
As I can see from CR the smart update was enabled and that is why operator gets images from version service and uses them. If you want to use custom images you need to disable it. Please set 'never' for
option.
Jira Bot September 23, 2021 at 11:57 AM
Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.
申祥瑞 August 25, 2021 at 4:03 AM
Thank you very much for your reply
Yes, as you said, don't have that field in `pitr` in standard cr.yaml
But when I applied the cr_itd-demo-db-pxc.yaml.yaml in the appendix to the v1.20.4 k8s cluster, I found that some of the set image fields have taken effect, and some have not taken effect. (But the strange thing is that the imagePullPolicy is in effect, only the image field part is not in effect)
For more information, please check the nearby cr_itd-demo-db-pxc.yaml.yaml and StatefulSet_itd-demo-db-pxc.yaml I added
Bulat Zamalutdinov August 24, 2021 at 8:44 AM
hi
Pitr using the image, specified in `backup` section.
Since we don't have that field in `pitr` section, webhook denies applying the wrong CR
Details
Details
Details
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist
hi everyone
I have encountered some problems using the pxc operator in k8s v1.20.4
Because of the time zone issue, I made some changes to the image, so I had to specify the image of all components in cr.yaml, including the image of pitr and imagePullPolicy of course
Some of the contents of my cr.yaml are as follows:
backup:
image: it/percona-xtradb-cluster-operator:1.9.0-pxc8.0-backup_cst
imagePullPolicy: IfNotPresent
pitr:
enabled: True
image: it/percona-xtradb-cluster-operator:1.9.0-pxc8.0-backup_cst
imagePullPolicy: IfNotPresent
storageName: objectstorage-binlogbackup
timeBetweenUploads: 60
When executing kubectl apply -f cr.yaml, the error is as follows:
Error from server: error when creating "cr.yaml": admission webhook "validationwebhook.pxc.percona.com" denied the request: json: unknown field "image"
Error from server: error when creating "cr.yaml": admission webhook "validationwebhook.pxc.percona.com" denied the request: json: unknown field "imagePullPolicy"
After investigation, kubectl apply -f cr.yaml can be executed successfully only if the image and imagePullPolicy configurations in the pitr part are deleted.
At present, this restriction is not very user-friendly, because the user needs to be able to modify the image url of all components