github.com/1aal/kubeblocks@v0.0.0-20231107070852-e1c03e598921/docs/release_notes/v0.4.0/v0.4.0.md (about)

     1  # KubeBlocks 0.4.0 (2023-03-10)
     2  
     3  We are happy to announce the release of KubeBlocks 0.4.0 with some exciting new features and improvements. KubeBlocks v0.4.0 now supports PostgreSQL databases and has improved resource isolation, security, and usability. 🚀 🎉 🎈
     4  
     5  ## Highlights
     6  
     7  * KubeBlocks supports PostgreSQL v14.7 [#11227](https://github.com/apecloud/kubeblocks/issues/1127)
     8    
     9    After the support of the world's most popular open source database MySQL, KubeBlocks now supports the world's most advanced open source database PostgreSQL. PostgreSQL offers a wide range of data types and excels at managing spatial locations and geographic information. To provide a seamless, ready-to-use experience for users, PostgreSQL clusters created by KubeBlocks come with popular plugins such as PostGIS pre-installed by default.
    10    Currently, the PostgreSQL clusters created by KubeBlocks do not support cross-AZ high availability, and there is a risk of data loss in extreme scenarios where block devices are damaged. As a result, they are recommended only for testing purposes. However, in future versions, data reliability, service availability, and feature richness will continue to be enhanced.
    11  
    12  * KubeBlocks simplifies resource isolation settings at the node level. [#1533](https://github.com/apecloud/kubeblocks/issues/1533)
    13    
    14    Stateful services can be impacted by "noisy neighbors," but KubeBlocks has addressed this issue by enabling users to run database clusters on specific Node groups through Taint and Label settings, while still being able to run with "noisy neighbors" when resources are scarce. This improvement gives users greater control over isolation without adding complexity to the interaction, and without requiring them to set affinity.
    15  
    16  * KubeBlocks provides an Endpoint for being accessed outside of the K8s cluster. [#1024](https://github.com/apecloud/kubeblocks/issues/1024), [#1144](https://github.com/apecloud/kubeblocks/issues/1144)
    17    You may need to access KubeBlocks database clusters through VPC or a public Endpoint in scenarios such as PoC or data migration. However, to apply for an Endpoint, users need to learn about the cloud vendor's network ACLs, Load Balancer configuration, and identity and permission management systems. To reduce the learning curve for users, KubeBlocks integrates with the cloud vendor's Load Balancers, enabling smooth network access with just one expose command executed on the target database cluster.
    18  
    19  ## Acknowledgements
    20  
    21  Thanks to everyone who made this release possible!
    22  
    23  @iziang, @ldming, @lynnleelhl, @nashtsai, @wangyelei, @weicao, @xuriwuyun, @Y-Rookie, @heng4fun
    24  
    25  ## What's Changed
    26  
    27  ### New Features
    28  
    29  #### PostgreSQL
    30  
    31  * Lifecycle management in Standalone mode includes creation, deletion, restart, vertical scaling, and horizontal scaling.  [#1324](https://github.com/apecloud/kubeblocks/issues/1324), [#1322](https://github.com/apecloud/kubeblocks/issues/1322)
    32  * Full backups based on snapshots, which can be initiated manually or automatically. These snapshot backups can be completed within two minutes without affecting the performance of the instance. [#901](https://github.com/apecloud/kubeblocks/issues/901)
    33  * Full recovery based on snapshots. With sufficient resources, users can quickly restore the full amount of data to the new database cluster.
    34  
    35  #### Compatibility
    36  - Pass the AWS EKS v1.22 / v1.23 / v1.24 / v1.25 compatibility test. 
    37  
    38  #### Maintainability
    39  
    40  - Users are able to modify the parameter configuration of the database cluster. When modifying parameters, kbcli checks the validation of the parameter settings. They can also compare differences between the current and previous versions through historical records. [#849](https://github.com/apecloud/kubeblocks/issues/849)
    41    - Parameters of MySQL are more than 500, including max_connections, max_allowed_packet, table_open_cache and so on.
    42    - Parameters of PostgreSQL are more than 350, including max_connections, shared_buffers, wal_level and so on. [#1323](https://github.com/apecloud/kubeblocks/issues/1323)
    43  - Supports manual start or stop of database clusters by users to save  computing resources, and data or backups will not be deleted during the stopped period.
    44  
    45  #### Easy of Use
    46  
    47  - Using kbcli to install KubeBlocks, kbcli will choose the suitable addons to install according to running environment.  [#928](https://github.com/apecloud/kubeblocks/issues/928), [#1354](https://github.com/apecloud/kubeblocks/issues/1354)
    48  - Using kbcli to install KubeBlocks,  the namespace is by default kb-system. You can specify the namespace. Note: The database cluster is created in default namespace or specified namespace.  [#1371](https://github.com/apecloud/kubeblocks/issues/1371)
    49  - Using kbcli to create database clusters, if the cluster name is not specified, the system generates cluster name.  [#792](https://github.com/apecloud/kubeblocks/issues/792)
    50  - Using kbcli to create database clusters, you can use--set to configure resources of the cluster, including CPU, memory, storage size, and replica numbers.[#1337](https://github.com/apecloud/kubeblocks/issues/1337)
    51  - kbcli playground supports the one-click launch of AWS EKS runtime environment to experience the full set of KubeBlocks functions.   [#1142](https://github.com/apecloud/kubeblocks/issues/1142)
    52  
    53  #### Resource Isolation
    54  
    55  - KubeBlocks has built-in affinity and toleration configurations on both data plane and control plane to prevent stateless  applications from competing for KubeBlocks' runtime resources. [#1533](https://github.com/apecloud/kubeblocks/issues/1533)
    56  - KubeBlocks' database cluster introduces tenant types, where dedicated  tenancy can avoid the behavior of database clusters competing for  runtime resources with each other. [#931](https://github.com/apecloud/kubeblocks/issues/931)
    57  
    58  #### Observability
    59  
    60  - Support PostgreSQL monitoring, including [#902](https://github.com/apecloud/kubeblocks/issues/902)
    61    - Check Connections, Tuples, Queries, Transactions & WAL, Conflicts & Locks, Buffers & Blocks operations, Temp files, Database Size and the CPU, memory, traffic of pod.
    62    - Built-in common alarm rules, including abnormal events such as restart, slow query, increasing in the number of connections, decreasing in Cache hit rate, deadlock, and AutoVacuum etc.
    63  - Support customized robot alarms for Slack, Feishu, Wechat and DingTalks.  [#1536](https://github.com/apecloud/kubeblocks/issues/1536)
    64  
    65  
    66  ### Bug Fixes
    67  
    68  - ginkgo v2 error fix ([#1011](https://github.com/apecloud/kubeblocks/pull/1011), @lynnleelhl)
    69  - fixed deploy/postgresqlcluster/templates/cluster.yaml template error ([#1043](https://github.com/apecloud/kubeblocks/pull/1043), @nashtsai)
    70  - fixed PostgreSQL chart conf volume error ([#1045](https://github.com/apecloud/kubeblocks/pull/1045), @nashtsai)
    71  - terminate the cli installation if error occurs ([#1147](https://github.com/apecloud/kubeblocks/pull/1147), @ldming)
    72  - build kbcli with CGO_ENABLED=0 ([#1339](https://github.com/apecloud/kubeblocks/pull/1339), @ldming)
    73  - container run as root and rename cd.name ([#1461](https://github.com/apecloud/kubeblocks/pull/1461), @ZhaoDiankui)
    74  - check sts and pods revision ([#1470](https://github.com/apecloud/kubeblocks/pull/1470), @heng4fun)
    75  - install nyancat failed when KubeBlocks repo does not exist ([#1474](https://github.com/apecloud/kubeblocks/pull/1474), @heng4fun)
    76  
    77  ## Breaking changes
    78  
    79  - Breaking changes between v0.4 and v0.3. Uninstall v0.3 before installing v0.4. 
    80    - Resource group name changes from dbaas.kubeblocks.io to apps.kubeblocks.io.