Community Monthly Report for May 2024

Overview

In May, KubeBlocks released v0.8.3 and continued the development of v0.9.0. The major updates are supporting cross-cluster referencing of configuration objects and NodeCountCluster. The community also fixed related defects.

Over the past month, the community merged 170 PRs, and resolved 133 issues, with contributions from 24 developers.

Highlights

• #7153 Supported to reference config across clusters.
• #7258 Supported NodeCountScaler.

Bug Fixes

• #7475 Fixed the crash issue after executing a switchover for MongoDB.
• #7447 Adapted rolecheck to accommodate cluster initialization for some database engines.
• #7365 Supported PVC to create idempotent.
• #7352 Added labels to distinguish KubeBlocks from dataprotection.
• #7323 Fixed the issue that the configmap 'xxx-rsm-env' was not found.
• #7299 Added lorry ports to the host network.
• #7256 Removed the validation for the cluster component spec in webhook.
• #7266 Fixed the issue that there were duplicate volume mounts in the config-manager container.

New Contributors

👏 Let's welcome

💙 @d976045024, duiniwukenaihe, starnop 💙!

Nice to have you here in the KubeBlocks community. All of them merged their first PR to KubeBlocks last month. Thanks for the contributions!

Good First Issues

We call for more developers to participate in the collaborative development of KubeBlocks. Starting with good first issues, we hope to build the next-generation database management platform with each and every one of you! Claim now 👇

• #7229 [Improvement] Specify backup/restore PORT by name
• #7031 [Improvement] doc API opsrequest.spec.restoreSpec.restoreTimeStr

Related links:

• Good first issue
• Contributing to KubeBlocks
• Developing KubeBlocks

Feel free to join the GitHub Discussion or the KubeBlocks Slack group!