Get a demo
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Get a quote
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Try for free
I hereby consent to the processing of my personal data specified herein by CROC, for the purposes and within the scope set forth by the Personal Data Protection legislation of the Russian Federation, in conjunction with the activities performed and for an indefinite term.
Preferred communication method
Know about updates

Ansible Dynamic Inventory support and other update of CROC Cloud

31.08.2021 2 minutes 46

You can now deploy Kubernetes clusters version 1.20.9 in the CROC Cloud. 

You can read what's new in release 1.20 on its official page. Instead, we want to tell you more about our other updates.

Ansible Dynamic Inventory support

You can now use dynamic inventory to manage virtual infrastructure in CROC Cloud. Ansible Dynamic Inventory provides the current list of available instances that meet specified criteria. You can group instances by tags, availability zones, VPCs, IDs, and more, and apply the desired commands and playbook scripts to them. For more information about Ansible Dynamic Inventory, see documentation

SchedulingDisabled state is synchronized between Kubernetes cluster and CROC Cloud

The master nodes of a Kubernetes cluster are no longer recreated automatically if they are in maintenance. For maintenance, such as updating the OS kernel, a master node has to be put in the SchedulingDisabled state. The cluster-manager (our cluster monitoring application) now synchronizes the SchedulingDisabled state between the Kubernetes cluster and CROC Cloud and does not recover such nodes if they become unavailable. 

For new clusters, the state is synchronized automatically. To activate synchronization on existing clusters, run the following command on any master node:
kubectl apply -f https://storage.cloud.croc.ru/kaas/v7/deployment/cluster-manager/cluster-manager.yaml

To view the current state of the master nodes, open the Instances tab on the cluster page. 

Learn more in documentation.

Other new features

In the instance wizard, the default virtualization type, hvm, is now explicitly specified. The virtualization type for an instance can later be changed from the Information tab on the instance page when the instance is in a StoppedError, or Failed state.

Mentioned services

  1. CROC Public Cloud

Don't miss the most important, interesting and helpful posts of the week

Success

scrollup