From 2e029d06fb2a3a305e039076f8fba98608ad93a4 Mon Sep 17 00:00:00 2001 From: dbazhenov Date: Mon, 29 Apr 2024 11:43:06 +0000 Subject: [PATCH] deploy: a27a3e8b531d3e32003a7af09217fd4530835d23 --- .../percona-monthly-bug-report-february/march-2024/index.html | 4 ++-- blog/index.html | 2 +- events/index.html | 2 +- events/percona-live/index.html | 2 +- index.xml | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/index.html b/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/index.html index 399e0d262..fcae2935a 100644 --- a/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/index.html +++ b/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/index.html @@ -48,7 +48,7 @@ evs.install_timeout(max) = 16s

Please note that 15s is not a hard limit and is determined by evs.inactive_timeout

We have set wsrep_provider_options=“evs.install_timeout=PT15S” for all nodes in the test environment and are now unable to reproduce the issue. So, we are on some timeout boundaries, and the above configuration parameters were introduced to fine-tune in such environments.

PXC-4367: Innodb semaphore wait timeout failure seen after upgrade from 8.0.34 to 8.0.35. This issue is a possible side effect of this patch, Where PXC node acts as the async replica to some master and in parallel, the row is updated on PXC node and via replication, the PXC node hangs. To avoid the issue, upgrading to PXC 8.0.36 is recommended.

Reported Affected Version/s: 8.0.35-27

Fixed Version: 8.0.36-28

PXC-4363: Concurrent CREATE and DROP USER queries on different nodes lead to permanent lock.

| 16 | system user  | db1 | Query | 411 | Waiting for table metadata lock | drop user IF EXISTS `msandbox_rw11`@`localhost` | 411380 | 0 |   
 

These queries cannot be cancelled or killed, and nodes refuse to be gracefully restarted. The shutdown is stuck with this forever. Only the forcible service kill helps restore the cluster.

2024-01-18T17:49:24.470428Z 0 [Note] [MY-000000] [Galera] Closing slave action queue.
-

Reported Affected Version/s: 8.0.35-27

Fixed Version: The fix is expected to be included in an upcoming release of Percona Servers.

PXC-4399: FLUSH TABLES during writes to the table with unique keys stall the cluster node; due to the stall, it’s not possible to abort/kill any of the above connections. The node sends a permanent flow control pause. The only way to get out of this stall is to kill the node.

Reported Affected Version/s: 8.0.33-25, 8.0.35-27

Fixed Version: The fix is expected to be included in an upcoming release of Percona Servers.

PXC-4418: In MySQL, the optimizer creates a temp table definition with indexes, where 2 of them have the same name (<auto_key2>, <auto_key1>, <auto_key2>). When the query is executed, a temp table is created, then MySql tries to access <auto_key2>. In InnoDB, we search for index by name (dict_table_get_index_on_name()), which returns the wrong <auto_key2>. Then row_sel_convert_mysql_key_to_innobase() crashes as structures are not aligned. Please note this bug affects only very complicated queries with many JOINs and subqueries. To repeat this bug, the internal temporary table needs to be created at least for two parts of the query.

Reported Affected Version/s: 8.0.32-24, 8.0.34-26

Fixed Version: 8.0.36-28

Percona Toolkit

PT-2190:The pt-show-grants use SHOW CREATE USER command to obtain grants from the MySQL server. By default, this query returns values as they are stored in the mysql.user table. When using caching_sha256_password, such hash of the password could contain a special character. Therefore, it would not be possible to use output printed by pt-show-grants to re-create users in the database. Since version 3.6.0, pt-show-grants checks if it runs against MySQL version 8.0.17 or higher and sets session option print_identified_as_hex to true before running SHOW CREATE USER command. This allows to print commands that could be used to re-create users.

Reported Affected Version/s: 3.5.1

Fixed Version: 3.6.0 [It is expected to be released soon]

PT-2215: pt-table-sync does not recognize the privileges in roles for MariaDB

Reported Affected Version/s: 3.5.2

Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

PT-2316: pt-config-diff with –pid option is broken with “Can’t locate object method “make_PID_file” via package “Daemon” at /usr/bin/pt-config-diff line 5522” on Ubuntu 20.04

Reported Affected Version/s: 3.5.7

Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

PT-2314: pt-online-schema-change fails due to duplicate constraint names when it attempts to make a table copy for alteration.

Reported Affected Version/s: 3.5.7

Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

Workaround/Fix: Do not duplicate constraints name.

PT-2322: pt-mysql-summary does not detect jemalloc when installed as systemd.

Reported Affected Version/s: 3.5.6, 3.5.7

Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

PMM [Percona Monitoring and Management]

PMM-11583: On MySQL 8.0, innodb_redo_log_capacity supersedes innodb_log_files_in_group and innodb_log_file_size, which eventually breaks InnoDB Logging graphs. Due to this issue, the user can not determine whether the combined InnoDB redo log file size has to be increased or not.

Reported Affected Version/s: 2.41.1

Fixed Version: 2.41.3 [It is expected to be released soon]

PMM-13017: For certain db.collection.find(query, projection, options) queries, the Explain tab for QAN returns an error message saying, “error decoding key command: invalid JSON input; expected value for 64-bit integer.” Please note this issue specifically affects MongoDB monitoring.

Reported Affected Version/s: 2.35.0, 2.37.1, 2.41.1

Fixed Version: The fix is expected to be included in an upcoming release of PMM

PMM-12522: When adding data relatively large chunks of data to MongoDB sharded cluster, pmm-agent log starts flooded with “level=error msg="cannot create metric for changelog… & level=error msg="Failed to get database names:…” which eventually shows MongoS as disconnected in PMM UI (PMM-Inventory/Services).

Reported Affected Version/s: 2.39.0, 2.40.0, 2.41.1

Fixed Version: 2.41.3 [It is expected to be released soon]

PMM-12880: pmm-admin –tls-skip-verify does not work when x509 authentication is used.

Reported Affected Version/s: 2.41.0

Fixed Version: 2.41.3 [It is expected to be released soon]

PMM-12989: PMM agent logs flooded with wrong log entries when monitoring auth-enabled arbiters. Please note this issue specifically affects MongoDB monitoring.

Reported Affected Version/s: 2.41.1

Fixed Version: 2.41.3 [It is expected to be released soon]

Percona XtraBackup

PXB-3251: When PXB fails to load the encryption key, the xtrabackup_logfile is still created in the target dir. This causes a second attempt at running PXB to fail with a new error. The xtrabackup_logfile file contains data needed to run the –prepare process. The bigger this file is, the longer the –prepare process will take to finish. So, PXB should not create any files on disk until the encryption key is loaded.

Reported Affected Version/s: 8.0.35-30

Fixed Version: The fix is expected to be included in future releases of PXB

Percona Kubernetes Operator

K8SPG-496: When a PostgreSQL Database is set to a paused state via spec, the operator waits until all backups for the Database finish. After the backups finish, the PostgreSQL Database shall be paused, which is not happening.

Reported Affected Version/s: 2.3.0

Fixed Version: 2.3.1

K8SPG-494: High vulnerabilities found for pgbackrest, Postgres & pgbouncer package.

For pgbackrest and postgres: CVE-2023-38408

For pgbouncer: CVE-2023-32067

Reported Affected Version/s: 2.3.0

Fixed Version: 2.3.1

K8SPG-521: The upgrade path described in the documentation leads to disabled built-in extensions(pg_stat_monitor, pg_audit).

Reported Affected Version/s: 2.3.1

Fixed Version: 2.4.0 [It is expected to be released soon]

K8SPG-522: Cluster is broken if PG_VERSION file is missing during the upgrade from 2.2.0 to 2.3.1.

Reported Affected Version/s: 2.3.1

Fixed Version: 2.4.0 [It is expected to be released soon]

Workaround/Fix: In order to fix the issue, please do the following:

  1. Create PG_VERSION with contents 14 in DB instance pod.

    echo 14 > /pgdata/pg14/PG_VERSION

  2. Apply crd and rbac

    kubectl apply --force-conflicts --server-side -f crd.yaml

    kubectl -n operatornew apply --force-conflicts --server-side -f rbac.yaml

  3. Restart the operator deployment.

    kubectl -n operatornew rollout restart deployment percona-postgresql-operator

  4. At this moment, patronictl show-config starts to enlist extensions.

    $ kubectl -n operatornew exec cluster1-instance1-gsvs-0 -it -- bash
    +

    Reported Affected Version/s: 8.0.35-27

    Fixed Version: The fix is expected to be included in an upcoming release of Percona Servers.

    PXC-4399: FLUSH TABLES during writes to the table with unique keys stall the cluster node; due to the stall, it’s not possible to abort/kill any of the above connections. The node sends a permanent flow control pause. The only way to get out of this stall is to kill the node.

    Reported Affected Version/s: 8.0.33-25, 8.0.35-27

    Fixed Version: The fix is expected to be included in an upcoming release of Percona Servers.

    PXC-4418: In MySQL, the optimizer creates a temp table definition with indexes, where 2 of them have the same name (<auto_key2>, <auto_key1>, <auto_key2>). When the query is executed, a temp table is created, then MySql tries to access <auto_key2>. In InnoDB, we search for index by name (dict_table_get_index_on_name()), which returns the wrong <auto_key2>. Then row_sel_convert_mysql_key_to_innobase() crashes as structures are not aligned. Please note this bug affects only very complicated queries with many JOINs and subqueries. To repeat this bug, the internal temporary table needs to be created at least for two parts of the query.

    Reported Affected Version/s: 8.0.32-24, 8.0.34-26

    Fixed Version: 8.0.36-28

    Percona Toolkit

    PT-2190:The pt-show-grants use SHOW CREATE USER command to obtain grants from the MySQL server. By default, this query returns values as they are stored in the mysql.user table. When using caching_sha256_password, such hash of the password could contain a special character. Therefore, it would not be possible to use output printed by pt-show-grants to re-create users in the database. Since version 3.6.0, pt-show-grants checks if it runs against MySQL version 8.0.17 or higher and sets session option print_identified_as_hex to true before running SHOW CREATE USER command. This allows to print commands that could be used to re-create users.

    Reported Affected Version/s: 3.5.1

    Fixed Version: 3.6.0 [It is expected to be released soon]

    PT-2215: pt-table-sync does not recognize the privileges in roles for MariaDB

    Reported Affected Version/s: 3.5.2

    Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

    PT-2316: pt-config-diff with –pid option is broken with “Can’t locate object method “make_PID_file” via package “Daemon” at /usr/bin/pt-config-diff line 5522” on Ubuntu 20.04

    Reported Affected Version/s: 3.5.7

    Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

    PT-2314: pt-online-schema-change fails due to duplicate constraint names when it attempts to make a table copy for alteration.

    Reported Affected Version/s: 3.5.7

    Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

    Workaround/Fix: Do not duplicate constraints name.

    PT-2322: pt-mysql-summary does not detect jemalloc when installed as systemd.

    Reported Affected Version/s: 3.5.6, 3.5.7

    Fixed Version: The fix is expected to be included in an upcoming release of Percona ToolKit.

    PMM [Percona Monitoring and Management]

    PMM-11583: On MySQL 8.0, innodb_redo_log_capacity supersedes innodb_log_files_in_group and innodb_log_file_size, which eventually breaks InnoDB Logging graphs. Due to this issue, the user can not determine whether the combined InnoDB redo log file size has to be increased or not.

    Reported Affected Version/s: 2.41.1

    Fixed Version: 2.41.3 [It is expected to be released soon]

    PMM-13017: For certain db.collection.find(query, projection, options) queries, the Explain tab for QAN returns an error message saying, “error decoding key command: invalid JSON input; expected value for 64-bit integer.” Please note this issue specifically affects MongoDB monitoring.

    Reported Affected Version/s: 2.35.0, 2.37.1, 2.41.1

    Fixed Version: The fix is expected to be included in an upcoming release of PMM

    PMM-12522: When adding data relatively large chunks of data to MongoDB sharded cluster, pmm-agent log starts flooded with “level=error msg="cannot create metric for changelog… & level=error msg="Failed to get database names:…” which eventually shows MongoS as disconnected in PMM UI (PMM-Inventory/Services).

    Reported Affected Version/s: 2.39.0, 2.40.0, 2.41.1

    Fixed Version: 2.41.3 [It is expected to be released soon]

    PMM-12880: pmm-admin –tls-skip-verify does not work when x509 authentication is used.

    Reported Affected Version/s: 2.41.0

    Fixed Version: 2.41.3 [It is expected to be released soon]

    PMM-12989: PMM agent logs flooded with wrong log entries when monitoring auth-enabled arbiters. Please note this issue specifically affects MongoDB monitoring.

    Reported Affected Version/s: 2.41.1

    Fixed Version: 2.41.3 [It is expected to be released soon]

    Percona XtraBackup

    PXB-3251: When PXB fails to load the encryption key, the xtrabackup_logfile is still created in the target dir. This causes a second attempt at running PXB to fail with a new error. The xtrabackup_logfile file contains data needed to run the –prepare process. The bigger this file is, the longer the –prepare process will take to finish. So, PXB should not create any files on disk until the encryption key is loaded.

    Reported Affected Version/s: 8.0.35-30

    Fixed Version: The fix is expected to be included in future releases of PXB

    Percona Kubernetes Operator

    K8SPG-496: When a PostgreSQL Database is set to a paused state via spec, the operator waits until all backups for the Database finish. After the backups finish, the PostgreSQL Database shall be paused, which is not happening.

    Reported Affected Version/s: 2.3.0

    Fixed Version: 2.3.1

    K8SPG-494: High vulnerabilities found for pgbackrest, Postgres & pgbouncer package.

    For pgbackrest and postgres: CVE-2023-38408

    For pgbouncer: CVE-2023-32067

    Reported Affected Version/s: 2.3.0

    Fixed Version: 2.3.1

    K8SPG-521: The upgrade path described in the documentation leads to disabled built-in extensions(pg_stat_monitor, pg_audit).

    Reported Affected Version/s: 2.3.1

    Fixed Version: 2.4.0 [It is expected to be released soon]

    K8SPG-522: Cluster is broken if PG_VERSION file is missing during the upgrade from 2.2.0 to 2.3.1.

    Reported Affected Version/s: 2.3.1

    Fixed Version: 2.4.0 [It is expected to be released soon]

    Workaround/Fix: In order to fix the issue, please do the following:

    1. Create PG_VERSION with contents 14 in DB instance pod.

      echo 14 > /pgdata/pg14/PG_VERSION

    2. Apply crd and rbac

      kubectl apply --force-conflicts --server-side -f crd.yaml

      kubectl -n operatornew apply --force-conflicts --server-side -f rbac.yaml

    3. Restart the operator deployment.

      kubectl -n operatornew rollout restart deployment percona-postgresql-operator

    4. At this moment, patronictl show-config starts to enlist extensions.

      $ kubectl -n operatornew exec cluster1-instance1-gsvs-0 -it -- bash
       
       Defaulted container "database" out of: database, replication-cert-copy, postgres-startup (init), nss-wrapper-init (init)
       
      @@ -77,5 +77,5 @@
           restore_command: pgbackrest --stanza=db archive-get %f "%p"
       
       shared_preload_libraries: pg_stat_monitor,pgaudit
      -
    5. Now extensions appear in the \dx output without pod restarts, but all Postgresql servers will be restarted:

    K8SPG-547: The pgbackrest container can’t use pgbackrest 2.50. This is because pgbackrest 2.50 requires libssh2.so.1, which requires epel. Without that fix, microdnf installs pgbackrest 2.48, which creates inconsistency with the Postgresql container.

    Reported Affected Version/s: 2.2.0

    Fixed Version: 2.4.0 [It is expected to be released soon]

    Workaround/Fix: This patch can be used until it is fixed.

    Summary

    We welcome community input and feedback on all our products. If you find a bug or would like to suggest an improvement or a feature, learn how in our post, How to Report Bugs, Improvements, New Feature Requests for Percona Products.

    For the most up-to-date information, be sure to follow us on Twitter, LinkedIn, and Facebook.

    Quick References:

    Percona JIRA

    MySQL Bug Report

    Report a Bug in a Percona Product

    Aaditya Dubey

    Database Performance & Bug Detective @ Percona | Ex - Oracle

    Highly experienced and seasoned MySQL Database Engineer with a proven record of strong database development and maintenance. Profoundly knowledgeable about a wide variety of databases. Excellent ability to work independently or as a part of the Team.

    See all posts by Aaditya Dubey »

    Discussion

    We invite you to our forum for discussion. You are welcome to use the widget below.

    +
  5. Now extensions appear in the \dx output without pod restarts, but all Postgresql servers will be restarted:

K8SPG-547: The pgbackrest container can’t use pgbackrest 2.50. This is because pgbackrest 2.50 requires libssh2.so.1, which requires epel. Without that fix, microdnf installs pgbackrest 2.48, which creates inconsistency with the Postgresql container.

Reported Affected Version/s: 2.2.0

Fixed Version: 2.4.0 [It is expected to be released soon]

Workaround/Fix: This patch can be used until it is fixed.

Summary

We welcome community input and feedback on all our products. If you find a bug or would like to suggest an improvement or a feature, learn how in our post, How to Report Bugs, Improvements, New Feature Requests for Percona Products.

For the most up-to-date information, be sure to follow us on Twitter, LinkedIn, and Facebook.

Quick References:

Percona JIRA

MySQL Bug Report

Report a Bug in a Percona Product

Aaditya Dubey

Database Performance & Bug Detective @ Percona | Ex - Oracle

Highly experienced and seasoned MySQL Database Engineer with a proven record of strong database development and maintenance. Profoundly knowledgeable about a wide variety of databases. Excellent ability to work independently or as a part of the Team.

See all posts by Aaditya Dubey »

Discussion

We invite you to our forum for discussion. You are welcome to use the widget below.

Share on LinkedIn
Share on Telegram

Did you like this post? Why not read more?

\ No newline at end of file diff --git a/blog/index.html b/blog/index.html index bcb1fe196..2e4f84977 100644 --- a/blog/index.html +++ b/blog/index.html @@ -2,5 +2,5 @@ ">

Latest articles

+

Latest articles

\ No newline at end of file diff --git a/events/index.html b/events/index.html index 7ded830c4..ba51895ee 100644 --- a/events/index.html +++ b/events/index.html @@ -2,5 +2,5 @@ ">
+
\ No newline at end of file diff --git a/events/percona-live/index.html b/events/percona-live/index.html index ac98bc12b..ef4527feb 100644 --- a/events/percona-live/index.html +++ b/events/percona-live/index.html @@ -2,5 +2,5 @@ ">

Percona Live Community Rooms

Percona Community worked together with other communities to organize Community Tracks at Percona Live.

Select a room to watch the content.

Full list of speakers on the Speakers page.

+

Percona Live Community Rooms

Percona Community worked together with other communities to organize Community Tracks at Percona Live.

Select a room to watch the content.

Full list of speakers on the Speakers page.

\ No newline at end of file diff --git a/index.xml b/index.xml index dfb5ed349..e04c93caf 100644 --- a/index.xml +++ b/index.xml @@ -1 +1 @@ -Percona Communityhttps://percona.community/Mon, 29 Apr 2024 11:05:09 -0000daily1enhttps://percona.community/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/Percona Monthly Bug Report: February/March 2024Mon, 29 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/https://percona.community/blog/2024/04/19/deploying-percona-everest-on-gcp-with-kubectl-for-windows-11-users/Deploying Percona Everest on GCP with Kubectl for Windows 11 UsersFri, 19 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/19/deploying-percona-everest-on-gcp-with-kubectl-for-windows-11-users/https://percona.community/blog/2024/04/17/release-roundup-april-17-2024/Release Roundup April 17, 2024Wed, 17 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/17/release-roundup-april-17-2024/https://percona.community/blog/2024/04/02/release-roundup-april-2-2024/Release Roundup April 2, 2024Tue, 02 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/02/release-roundup-april-2-2024/https://percona.community/blog/2024/03/27/creating-a-standby-cluster-with-the-percona-operator-for-postgresql/Creating a Standby Cluster With the Percona Operator for PostgreSQLWed, 27 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/27/creating-a-standby-cluster-with-the-percona-operator-for-postgresql/https://percona.community/blog/2024/03/26/open-door-mongodb-chats/Open Door MongoDB ChatsTue, 26 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/26/open-door-mongodb-chats/https://percona.community/blog/2024/03/18/release-roundup-march-18-2024/Release Roundup March 18, 2024Mon, 18 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/18/release-roundup-march-18-2024/https://percona.community/blog/2024/03/04/release-roundup-march-4-2024/Release Roundup March 4, 2024Mon, 04 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/04/release-roundup-march-4-2024/https://percona.community/blog/2024/03/04/setting-up-your-environment-for-kubernetes-operators-using-docker-kubectl-and-k3d/Setting Up Your Environment for Kubernetes Operators Using Docker, kubectl, and k3dMon, 04 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/04/setting-up-your-environment-for-kubernetes-operators-using-docker-kubectl-and-k3d/https://percona.community/blog/2024/02/21/release-roundup-february-21-2024/Release Roundup February 21, 2024Wed, 21 Feb 2024 00:00:00 +0000https://percona.community/blog/2024/02/21/release-roundup-february-21-2024/https://percona.community/blog/2024/02/19/percona-monthly-bug-report-january-2024/Percona Monthly Bug Report: January 2024Mon, 19 Feb 2024 00:00:00 +0000https://percona.community/blog/2024/02/19/percona-monthly-bug-report-january-2024/https://percona.community/blog/2024/01/26/unexpected-stalled-upgrade-to-mysql-8-0/Unexpected Stalled Upgrade to MySQL 8.0Fri, 26 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/26/unexpected-stalled-upgrade-to-mysql-8-0/https://percona.community/blog/2024/01/12/our-top-picks-from-the-kubernetes-release/Our Top Picks from the Kubernetes 1.29 ReleaseFri, 12 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/12/our-top-picks-from-the-kubernetes-release/https://percona.community/blog/2024/01/10/data-on-kubernetes-community-initiatives/Data on Kubernetes Community initiatives: Automated storage scalingWed, 10 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/10/data-on-kubernetes-community-initiatives/https://percona.community/blog/2024/01/10/volunteering-program-committee-data-kubernetes-europe/Volunteering as a Program Committee Member for Data on Kubernetes Day Europe 2024Wed, 10 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/10/volunteering-program-committee-data-kubernetes-europe/ \ No newline at end of file +Percona Communityhttps://percona.community/Mon, 29 Apr 2024 11:42:27 -0000daily1enhttps://percona.community/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/Percona Monthly Bug Report: February/March 2024Mon, 29 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/29/percona-monthly-bug-report-february/march-2024/https://percona.community/blog/2024/04/19/deploying-percona-everest-on-gcp-with-kubectl-for-windows-11-users/Deploying Percona Everest on GCP with Kubectl for Windows 11 UsersFri, 19 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/19/deploying-percona-everest-on-gcp-with-kubectl-for-windows-11-users/https://percona.community/blog/2024/04/17/release-roundup-april-17-2024/Release Roundup April 17, 2024Wed, 17 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/17/release-roundup-april-17-2024/https://percona.community/blog/2024/04/02/release-roundup-april-2-2024/Release Roundup April 2, 2024Tue, 02 Apr 2024 00:00:00 +0000https://percona.community/blog/2024/04/02/release-roundup-april-2-2024/https://percona.community/blog/2024/03/27/creating-a-standby-cluster-with-the-percona-operator-for-postgresql/Creating a Standby Cluster With the Percona Operator for PostgreSQLWed, 27 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/27/creating-a-standby-cluster-with-the-percona-operator-for-postgresql/https://percona.community/blog/2024/03/26/open-door-mongodb-chats/Open Door MongoDB ChatsTue, 26 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/26/open-door-mongodb-chats/https://percona.community/blog/2024/03/18/release-roundup-march-18-2024/Release Roundup March 18, 2024Mon, 18 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/18/release-roundup-march-18-2024/https://percona.community/blog/2024/03/04/release-roundup-march-4-2024/Release Roundup March 4, 2024Mon, 04 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/04/release-roundup-march-4-2024/https://percona.community/blog/2024/03/04/setting-up-your-environment-for-kubernetes-operators-using-docker-kubectl-and-k3d/Setting Up Your Environment for Kubernetes Operators Using Docker, kubectl, and k3dMon, 04 Mar 2024 00:00:00 +0000https://percona.community/blog/2024/03/04/setting-up-your-environment-for-kubernetes-operators-using-docker-kubectl-and-k3d/https://percona.community/blog/2024/02/21/release-roundup-february-21-2024/Release Roundup February 21, 2024Wed, 21 Feb 2024 00:00:00 +0000https://percona.community/blog/2024/02/21/release-roundup-february-21-2024/https://percona.community/blog/2024/02/19/percona-monthly-bug-report-january-2024/Percona Monthly Bug Report: January 2024Mon, 19 Feb 2024 00:00:00 +0000https://percona.community/blog/2024/02/19/percona-monthly-bug-report-january-2024/https://percona.community/blog/2024/01/26/unexpected-stalled-upgrade-to-mysql-8-0/Unexpected Stalled Upgrade to MySQL 8.0Fri, 26 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/26/unexpected-stalled-upgrade-to-mysql-8-0/https://percona.community/blog/2024/01/12/our-top-picks-from-the-kubernetes-release/Our Top Picks from the Kubernetes 1.29 ReleaseFri, 12 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/12/our-top-picks-from-the-kubernetes-release/https://percona.community/blog/2024/01/10/data-on-kubernetes-community-initiatives/Data on Kubernetes Community initiatives: Automated storage scalingWed, 10 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/10/data-on-kubernetes-community-initiatives/https://percona.community/blog/2024/01/10/volunteering-program-committee-data-kubernetes-europe/Volunteering as a Program Committee Member for Data on Kubernetes Day Europe 2024Wed, 10 Jan 2024 00:00:00 +0000https://percona.community/blog/2024/01/10/volunteering-program-committee-data-kubernetes-europe/ \ No newline at end of file