After Nutanix Karbon 2.0’s recent announcement, Nutanix launches the first update: Karbon 2.1.

The new version aims to respond to two of the most complex challenges of Kubernetes: networking and storage.

Integration of Calico into Nutanix Karbon 2.1

Connecting Kubernetes pod and making them accessible to other external services or networks can be difficult and requires the use of overlay and NAT networks. On a large scale, this can become extremely complex. Many cloud-native companies looking for a container network solution that can provide a consistent experience as well as functionality applicable to different Kubernetes environments, have chosen Calico.

Calico combines flexible networking capabilities with the pervasive application of security policies to provide a solution with native Linux kernel performance and cloud-native scalability. This solution has become the benchmark in open-source Kubernetes network technologies, as well as being required by most Nutanix customers using Karbon. That’s why from today, Calico is an integrated component of Karbon.

Thanks to this integration, Karbon users can benefit from simplified and native-based Kubernetes networking capabilities that provide a better throughput than Flannel or an overlay-based network plugin. Since Calico uses standard tools and the most well-known network protocols, problem detection and resolution is extremely easy for both network and system administrators.

In addition, Calico allows you to implement network policies with simplicity. For example, users can isolate their pod from each other and limit access to and from an application. Overall, users have a more accurate network control at the level of distribution of the application.

The integration of Calico in Karbon also led to the technological alliance with Tigera, a company that invented Project Calico, of which it is also the main maintainer.

Tigera is an open-core company that offers Calico Enterprise, a solution based on Project Calico and that includes features that allow multiple teams and companies to use Kubernetes in a safe production environment. Tigera’s technology is used by the most important SaaS companies and financial services, retail and gaming industries where security and compliance are key issues.

Clone and extend CSI volumes

Volume cloning, recently integrated in Kubernetes, is a key feature in data protection. Based on Kubernetes user documentation, the CSI (Container Storage Interface) Volume Cloning provides support to specify existing PVCs in the dataSource field to indicate that a user wants to clone a volume. At the time a volume is cloned in Kubernetes, an exact duplicate is created which can be used in the same way as the original volume.

The integration of this functionality into the CSI interface (included in Karbon) allows users to fully benefit from Nutanix cloning technology. Thanks to Nutanix, the application data is inserted at the time of cloning, reducing the configuration time and the use of the total space. In addition, if the application using the cloned volume requires a larger volume size, the CSI driver will increase the size of the cloned volume accordingly.

The ability to clone volumes allows users to quickly resolve problems related to state-complete containerized applications. It allows you to immediately duplicate data from an application running in order to detect a problem or test a new version of the application.

Extended APIs

With Karbon 2.1, users can also use their favorite tools and portals to run Karbon workflows. Kubernetes clusters can be created in self-service mode through Nutanix Calm, ServiceNow or any other portal that can make API calls.

Through the expanded Karbon APIs, users can provide Kubernetes on-demand clusters (for developer, project, etc.), and automate the collection of kubeconfig files for a given cluster. It is also possible to automate SSH access to cluster nodes, which is particularly useful for debugging.

Leave a Reply

Your email address will not be published.

You May Also Like