Skip to content

Commit

Permalink
KubeDB v2023.11.2 (#352)
Browse files Browse the repository at this point in the history
Signed-off-by: Tamal Saha <[email protected]>
Signed-off-by: DRoyyy <[email protected]>
Co-authored-by: DRoyyy <[email protected]>
  • Loading branch information
tamalsaha and DRoyyy authored Nov 3, 2023
1 parent c32090f commit 527e2bd
Show file tree
Hide file tree
Showing 2 changed files with 89 additions and 0 deletions.
Binary file added content/post/kubedb-v2023.11.2/hero.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
89 changes: 89 additions & 0 deletions content/post/kubedb-v2023.11.2/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
---
title: Announcing KubeDB v2023.11.2
date: "2023-11-02"
weight: 14
authors:
- Tamal Saha
tags:
- cloud-native
- dashboard
- database
- day-2-operations
- elasticsearch
- kafka
- kubedb
- kubedb-cli
- kubernetes
- mariadb
- mongodb
- mysql
- opensearch
- percona
- percona-xtradb
- pgbouncer
- postgresql
- prometheus
- proxysql
- redis
- security
---

We are pleased to announce the release of [KubeDB v2023.11.2](https://kubedb.com/docs/v2023.11.2/setup/). This post lists all the major changes done in this release since the last release. Find the detailed changelogs [HERE](https://github.com/kubedb/CHANGELOG/blob/master/releases/v2023.11.2/README.md). Let’s see the changes done in this release.

## Breaking Changes

### UpdateVersion ops request

We originally added `Upgrade` ops request to support database version upgrades. Later we introduced `UpdateVersion` ops request and deprecated the `Upgrade` ops request. The reason was that this ops request can be used to either upgrade or downgrade between minor or patch versions. In this release, we have remove the `Upgrade` fields from the ops request CRD schema.

### kubedb-catalog chart values

In this release we have modified the values file schema for `kubedb-catalog` chart to support private registries properly.

## CLI

In this release, a new command has been added to kubedb cli to support checking for alerts generated by Prometheus rules.

```bash
Examples:
kubectl dba get-alerts mongodb -n demo sample-mongodb --prom-svc-name=prometheus-kube-prometheus-prometheus --prom-svc-namespace=monitoring

Valid resource types include:
* elasticsearch
* mongodb
* mariadb
* mysql
* postgres
* redis

Options:
--prom-svc-name='':
name of the prometheus service

--prom-svc-namespace='':
namespace of the prometheus service

--prom-svc-port=9090:
port of the prometheus service
```

## What Next?

Please try the latest release and give us your valuable feedback.

- If you want to install KubeDB, please follow the installation instruction from [KubeDB Setup](https://kubedb.com/docs/v2023.11.2/setup).

- If you want to upgrade KubeDB from a previous version, please follow the upgrade instruction from [KubeDB Upgrade](https://kubedb.com/docs/v2023.11.2/setup/upgrade/).


## Support

To speak with us, please leave a message on [our website](https://appscode.com/contact/).

To receive product announcements, follow us on [Twitter](https://twitter.com/KubeDB).

To watch tutorials of various Production-Grade Kubernetes Tools Subscribe our [YouTube](https://www.youtube.com/c/AppsCodeInc/) channel.

Learn More about [Production-Grade Databases in Kubernetes](https://kubedb.com/)

If you have found a bug with KubeDB or want to request for new features, please [file an issue](https://github.com/kubedb/project/issues/new).

0 comments on commit 527e2bd

Please sign in to comment.