Issues
- Consider some mitigation for PS-9235K8SPXC-1397Resolved issue: K8SPXC-1397Slava Sarzhan
- PiTR labels not updated for existing deploymentsK8SPXC-1312natalia.marukovich
- Backup stalls with S3 upload network issueK8SPXC-1271Resolved issue: K8SPXC-1271Pavel Tankov
- backup can be marked as failed even if it finishes on second tryK8SPXC-1265Resolved issue: K8SPXC-1265ege.gunes
- PiTR restore fails if xtrabackup user password is changed in binary log filesK8SPXC-1263Resolved issue: K8SPXC-1263dmitriy.kostiuk
- kubectl rollout restart sts is not working with RollingUpdateK8SPXC-1260
- Use official proxysql and haproxy docker imagesK8SPXC-1259Resolved issue: K8SPXC-1259inel.pandzic
- Operator cannot clean replication's failover sources if replications have been stoppedK8SPXC-1256Resolved issue: K8SPXC-1256ege.gunes
- audit log rotation broken with logrotate in k8-pxc operatorK8SPXC-1255Resolved issue: K8SPXC-1255Slava Sarzhan
- Helm chart - watchNamespace doesn't workK8SPXC-1250
- Manual Backups Entirely Do Not Work in pxc-operatorK8SPXC-1241Resolved issue: K8SPXC-1241
- Upgrading Cluster Fails When Dataset Has Large Number Of TablesK8SPXC-1222Resolved issue: K8SPXC-1222ege.gunes
- SmartUpdate should never downgradeK8SPXC-1221
- k8s worker fault causes endless Terminating status for pxc pod and huge messages in logsK8SPXC-1216ege.gunes
- MySQL settings should be visible by Xtrabackup during restoreK8SPXC-1215Slava Sarzhan
- Add option to automatically cleanup jobs and associated podsK8SPXC-1214ege.gunes
- S3 backups deletion in custom S3 storage (minio) fails with x509 unknown ca certificateK8SPXC-1213Resolved issue: K8SPXC-1213
- Allow 2 way replicationK8SPXC-1212Slava Sarzhan
- backup has started to fail, and now fails each timeK8SPXC-1209Resolved issue: K8SPXC-1209
- Operator cannot delete backups on s3 with custom TLSK8SPXC-1205Resolved issue: K8SPXC-1205Andrii Dema
- Operator not cleaning up backups from s3K8SPXC-1201ege.gunes
- Misleading logic when AllowUnsafeConfig is set and explitic TLS issuer is not definedK8SPXC-1194Resolved issue: K8SPXC-1194
- Operator requests cert-manager to generate server certificates with `IsCA: True` setK8SPXC-1193Resolved issue: K8SPXC-1193Andrii Dema
- Consider implementing x509 authentication for internal usersK8SPXC-1181
- All connections made by the operator and/or any checks should use encrypted channelsK8SPXC-1180ege.gunes
- Operator can't use TLS encryption for system usersK8SPXC-1179Resolved issue: K8SPXC-1179Slava Sarzhan
- Update 'Design and architecture' documentationK8SPXC-1178Resolved issue: K8SPXC-1178
- Operator recreates secrets under proxysql -> haproxy switch if delete-proxysql-pvc is used.K8SPXC-1164Resolved issue: K8SPXC-1164Andrii Dema
- Can't delete cluster in init state if using finalizers.K8SPXC-1163Resolved issue: K8SPXC-1163Andrii Dema
- issue with monitoring proxysql in pmmK8SPXC-1162Resolved issue: K8SPXC-1162Tomislav Plavcic
- pmm stops monitoring haproxy pods after pmmserverkey changeK8SPXC-1161Resolved issue: K8SPXC-1161Andrii Dema
- cluster stuck initializing if one pod unready and passwords changedK8SPXC-1160inel.pandzic
- cluster status flapping on invalid password changeK8SPXC-1159Resolved issue: K8SPXC-1159inel.pandzic
- HorizontalPodAutoscaler does not workK8SPXC-1157Resolved issue: K8SPXC-1157Slava Sarzhan
- Add innodb_log_file_size to auto-tuningK8SPXC-1154
- Improve PITR restore statusK8SPXC-1151Resolved issue: K8SPXC-1151ege.gunes
- Mark backups in S3 bucket as PITR unreadyK8SPXC-1144Andrii Dema
- failed to send telemetry before the cluster startsK8SPXC-1141Resolved issue: K8SPXC-1141
- Cluster became ready when svc EXTERNAL-IP is still in pending state.K8SPXC-1135Resolved issue: K8SPXC-1135Andrii Dema
- upgrade-consistency test fails on EKS/Openshift because of readiness probe and dns issueK8SPXC-1094Resolved issue: K8SPXC-1094Ivan Pylypenko
40 of 40
Consider some mitigation for PS-9235
Done
General
Escalation
General
Escalation
Description
Environment
None
AFFECTED CS IDs
CS0044496
is blocked by
Created May 17, 2024 at 10:08 AM
Updated January 1, 2025 at 3:52 PM
Resolved December 19, 2024 at 8:11 PM
Activity
Show:
Eleonora ZinchenkoNovember 26, 2024 at 7:01 AM
Hi,
For history: the issue was in PS when using Vault v2:
The issue is not reproduced with PXC8.0.37. The pxc POD and cluster starts ok:
Started with 1 pod and then increased to 3:
and the default configuration of operator when TDE is enabled makes the cluster unusable. Please consider some kind of mitigation of it, as without it the cluster fails with:
Steps to reproduce:
01) Deploy cluster with size of 1.
02) Deploy cluster with size of 3 and then restart it.