May#

May 12#

Changes#

  • RabbitMQ message broker is now available as a PaaS service. It helps to automate the messaging platform deployment and can be found in the new Message Brokers category in the Service Store Documentation.

  • Now, you can use the web interface to manage lifecycles of objects in a bucket, e.g., set rules and retention periods for objects and their versions.

  • You can configure bucket alarms directly on the bucket page. Alarms will help you track critical changes in bucket parameters.

  • When logging in to the cloud, the user will see the project that he/she worked on during the previous session.

  • The Redis database and caching service supports cluster architecture using Sentinel monitoring service.

  • When creating a Patroni-based PostgreSQL cluster, you can now select the streaming replication mode: asynchronous, synchronous or strictly synchronous.

API#

  • For automated PaaS service deployment, you can use PaaS API methods. They help you manage all the services supported in K2 Cloud, including database and caching services, message brokers, search and analytics services.

    Using PaaS API methods, you can start services in an arbitrary configuration, modify their parameters and delete them, if necessary. You can also manage backup process if the service supports it.

Fixed#

  • A static route is not removed when a dynamic route with the same CIDR is added to the route table.

May 26#

Changes#

  • You can now create alarms for instances and volumes directly on the corresponding resource page.

  • Route tables have got limits on the number of static and dynamic routes.

  • IDs are displayed for load balancers, listeners, and target groups in the web interface.

API#

  • To work with the backup service API, a c2-bs client has been released.

Fixed#

  • In the ReplaceRoute method, a bug has been fixed, which could cause a random route to be removed.

  • When providing public access to an object in the bucket, a correct notification is displayed.