Skip to content

Add release blog for KubeDB-v2025.4.30 #505

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 9, 2025
Merged

Conversation

ArnobKumarSaha
Copy link
Member

No description provided.

Copy link

github-actions bot commented May 6, 2025

Visit the preview URL for this PR (updated for commit 0d282de):

https://blog-v1-hugo--pr505-kubedb-v2025-4-30-414i0y3m.web.app

(expires Fri, 16 May 2025 13:08:54 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: ddacb919f90a98185619681ef0da6429c962b808

@ArnobKumarSaha ArnobKumarSaha force-pushed the kubedb-v2025.4.30 branch 6 times, most recently from b5f80d1 to b4b51ca Compare May 7, 2025 12:47
@tamalsaha tamalsaha force-pushed the kubedb-v2025.4.30 branch 2 times, most recently from 31f9916 to f75eab5 Compare May 7, 2025 18:14
@tamalsaha tamalsaha force-pushed the kubedb-v2025.4.30 branch from f75eab5 to 733f448 Compare May 7, 2025 18:17
@appscode appscode deleted a comment from gitguardian bot May 7, 2025
Copy link

gitguardian bot commented May 7, 2025

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

- **Automated Provisioning**: GitOps pipelines create corresponding KubeDB CRs to provision databases based on Git-defined states.
- **Smart Reconciliation**: The GitOps controller detects and resolves discrepancies in database configurations, replicas, or versions.

We have also changed the way to enable gitops feature. Pass `--set kubedb-crd-manager.installGitOpsCRDs=true` in the kubedb installation process to enable this.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have also changed the way to enable gitops feature. -> The method for enabling the GitOps feature has also been updated:?
in the kubedb installation process to enable this. -> during the KubeDB installation process to enable this.?

```

### Valkey Support
KubeDB now supports **Valkey**, a high-performance Redis fork, with new images for versions **8.1.1**, **8.0.3**, **7.2.9**, and **7.2.5**. Valkey is provisioned under the `Redis` CRD for consistency.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

under the Redis CRD for consistency. -> under the existing Redis CRD for consistency.?


## MongoDB
### `mongodb+srv` style connection url support
From this release, users can connect to the mongodb using `mongosh "mongodb+srv://<user>:<pass>@<host>/<database>?tls=true&tlsCAFile=./db-ca.crt"` connection uri. We have added `db.spec.replicaSet.horizons` field to specify the server dns & pod CNAME records. Here is a sample:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From this release, users can connect to the mongodb using mongosh -> This release enables users to connect to MongoDB using the mongosh?

- zookeeper
---

KubeDB **v2025.4.30** is here, delivering enhanced performance, expanded database support, and streamlined management for Kubernetes-based database deployments. This release introduces new features, improved reliability, and broader GitOps integration, making database operations more efficient and production-ready.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delivering enhanced performance -> bringing enhanced performance?

Signed-off-by: Arnob kumar saha <[email protected]>
@tamalsaha tamalsaha merged commit 957ba32 into master May 9, 2025
6 checks passed
@ArnobKumarSaha ArnobKumarSaha deleted the kubedb-v2025.4.30 branch May 9, 2025 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants