Issues
- custom config from secret is not mounted to proxysqlK8SPXC-821Resolved issue: K8SPXC-821Mykola Marzhan
- HAProxy ready nodes missing in cr statusK8SPXC-811Resolved issue: K8SPXC-811Slava Sarzhan
- cannot delete a pvc backup which had delete-s3-backup finalizer specifiedK8SPXC-726Resolved issue: K8SPXC-726Bulat Zamalutdinov
- deleting a backup from S3 doesn't work if endpointUrl includes ending slashK8SPXC-710Resolved issue: K8SPXC-710Pavel Kasko
- PITR is constantly re-uploading all binlogs after cluster restoreK8SPXC-707Resolved issue: K8SPXC-707Bulat Zamalutdinov
- PITR backup doesn't allow specifying endpointUrl for AWS S3K8SPXC-684Resolved issue: K8SPXC-684
- operator crashes if non-existing storage name specified for PITRK8SPXC-681Resolved issue: K8SPXC-681Maksim Dudin
- PITR ERROR collect binlog files - converting NULL to string is unsupportedK8SPXC-645Resolved issue: K8SPXC-645Bulat Zamalutdinov
- PITR collector loses connection to PXC, cannot do restoreK8SPXC-621Resolved issue: K8SPXC-621Bulat Zamalutdinov
- PITR put object: Your proposed upload is smaller than the minimum allowed sizeK8SPXC-615Resolved issue: K8SPXC-615Bulat Zamalutdinov
- PITR starts failing if PXC pod-0 executes init/SSTK8SPXC-611Resolved issue: K8SPXC-611Maksim Dudin
- PITR pod starts failing when cluster scaledK8SPXC-610Resolved issue: K8SPXC-610Maksim Dudin
- validation web hook configuration is not removed when operator deletedK8SPXC-604Resolved issue: K8SPXC-604Bulat Zamalutdinov
- PITR doesn't store all needed binlog entriesK8SPXC-593Resolved issue: K8SPXC-593Maksim Dudin
- PITR option transaction-gtidSet doesn't workK8SPXC-584Resolved issue: K8SPXC-584
- date option for PITR doesn't restore up to selected timeK8SPXC-583Resolved issue: K8SPXC-583
- pitr pod fails if xtrabackup password is rotatedK8SPXC-582Resolved issue: K8SPXC-582Maksim Dudin
- pause option or deleting CR doesn't stop the PITR podK8SPXC-581Resolved issue: K8SPXC-581Maksim Dudin
- operator throws error for validation webhook when not in cluster-wide modeK8SPXC-578Resolved issue: K8SPXC-578Bulat Zamalutdinov
- PITR backup fails if AWS S3 endpoint not specifiedK8SPXC-572Resolved issue: K8SPXC-572Maksim Dudin
- The secrets are not updated/synced correctly in case of HAProxy deploymentK8SPXC-552Resolved issue: K8SPXC-552Maksim Dudin
- haproxy stuck and not restarted (no liveness probe)K8SPXC-544Resolved issue: K8SPXC-544Slava Sarzhan
- Wrong custom HAProxy configuration breaks the PodK8SPXC-543Resolved issue: K8SPXC-543Slava Sarzhan
- cannot upgrade from 1.6.0 to 1.7.0 because of issue with calling a webhookK8SPXC-538Resolved issue: K8SPXC-538Bulat Zamalutdinov
- validationwebhook denied the request unknown field "accessModes"K8SPXC-537Resolved issue: K8SPXC-537Bulat Zamalutdinov
- smart update in cluster wide adds version service check job repeatedlyK8SPXC-520Resolved issue: K8SPXC-520Pavel Kasko
- Unable to create backup when using cluster-wide operatorK8SPXC-500Resolved issue: K8SPXC-500Slava Sarzhan
- fix primary detection in cluster-wide if HAProxy enabledK8SPXC-499Resolved issue: K8SPXC-499Mykola Marzhan
- Monitor user SERVICE_CONNECTION_ADMIN grant not added on upgrade from 1.5.0 to 1.6.0K8SPXC-480Resolved issue: K8SPXC-480Maksim Dudin
- ssl handshake issue when upgrading from 1.5.0 to 1.6.0K8SPXC-479Resolved issue: K8SPXC-479Slava Sarzhan
- Smart Update ErrorK8SPXC-477Resolved issue: K8SPXC-477Pavel Kasko
- smartUpdate fails to fetch version if PXC patch version incorrect and higher than last knownK8SPXC-476Resolved issue: K8SPXC-476Pavel Kasko
- Haproxy can spawn check_pxc.sh more than once that makes logs unreadableK8SPXC-424Resolved issue: K8SPXC-424Slava Sarzhan
- pods not restarted if custom mongo config is updated inside secret or configmapK8SPSMDB-496Resolved issue: K8SPSMDB-496Mykola Marzhan
- pods are not restarted if custom mongo config is updatedK8SPSMDB-492Resolved issue: K8SPSMDB-492Sergey Pronin
- restore with backupSource doesn't error if destination for full backup not specifiedK8SPSMDB-480Resolved issue: K8SPSMDB-480ege.gunes
- major downgrade is not possible when FCV is not upgraded to new versionK8SPSMDB-455Resolved issue: K8SPSMDB-455
- cluster breaks if skipping major upgradesK8SPSMDB-450Resolved issue: K8SPSMDB-450Pavel Kasko
- setFCV option doesn't change version in replica set major upgradeK8SPSMDB-449Resolved issue: K8SPSMDB-449Pavel Kasko
- operator should check if balancer running before starting the restore processK8SPSMDB-414Resolved issue: K8SPSMDB-414Pavel Kasko
- test database is marked as a system databaseK8SPSMDB-409Resolved issue: K8SPSMDB-409Pavel Kasko
- operator tries to add shard repeatedly even when already added when arbiters usedK8SPSMDB-408Resolved issue: K8SPSMDB-408Pavel Kasko
- Add logic for syncing restore with mongosK8SPSMDB-404Resolved issue: K8SPSMDB-404Pavel Kasko
- running multiple replica sets without sharding enabled should be prohibitedK8SPSMDB-402Resolved issue: K8SPSMDB-402Pavel Kasko
- mongos fails when allowUnsafeConfiguration=true and without TLS enabledK8SPSMDB-399Resolved issue: K8SPSMDB-399Pavel Kasko
- wrong cluster status after unsuccessful shard removalK8SPSMDB-398Resolved issue: K8SPSMDB-398ege.gunes
- disabling or enabling sharding with two or more shards should not be allowedK8SPSMDB-397Resolved issue: K8SPSMDB-397Pavel Kasko
- sharding - The server certificate does not match the remote host nameK8SPSMDB-393Sergey Pronin
- shard never removed without clear reason in the logsK8SPSMDB-392Resolved issue: K8SPSMDB-392Pavel Kasko
- PSMDB object status showing shard after successful removalK8SPSMDB-391Resolved issue: K8SPSMDB-391Pavel Kasko
50 of 70
custom config from secret is not mounted to proxysql
Done
General
Escalation
General
Escalation
Description
Environment
None
Attachments
2
Smart Checklist
Details
Assignee
Mykola MarzhanMykola Marzhan(Deactivated)Reporter
Tomislav PlavcicTomislav PlavcicFix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Mykola Marzhan
Mykola Marzhan(Deactivated)Reporter
Tomislav Plavcic
Tomislav PlavcicFix versions
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created July 12, 2021 at 8:44 AM
Updated March 5, 2024 at 5:47 PM
Resolved August 9, 2021 at 8:09 AM
Before starting a cluster I have created a following secret in the namespace:
pods look like this:
Here's pod describe and stateful set for proxysql.
If I didn't do something wrong it seems like the custom config is not mounted and it's not used in proxysql pod.
The same works for me with haproxy.
Also I think this part is probably wrong and should be disabled in the e2e test: https://github.com/percona/percona-xtradb-cluster-operator/blob/main/e2e-tests/haproxy/conf/haproxy-proxysql.yml#L56-L103
Because it should test if the config is used from the secret and not if applied from cr.yaml (which works)