Diamanti, a provider of turn-key Kubernetes hyper-converged platform, releases version 3.3.0 for its Ultima Accelerator product family. The enhancements that are part of this release build on top of Diamanti’s best-in-class storage and networking features, providing predictable performance, low latencies and I/O isolation that eliminates noisy-neighbour problems.
What’s New in the Release
Read-Write-Many Support
With 3.3.0 release Diamanti introduces support for RWX (ReadWriteMany) volumes through its CSI driver. ReadWriteMany volumes are volumes that can be mounted in a Read/Write fashion simultaneously into a number of pods. RWX volumes particularly useful for web and app servers that serve the same files (Shared Database). RWX volumes are also useful for CI systems like Jenkins which can use a shared volume for artifact storage rather than unnecessarily duplicating data and impacting CI performance. NFS protocol which supports exporting the volume to multiple users for concurrent access is used to support Diamanti’s RWX volumes feature. For a PVC created with RWX access mode, NFS server is automatically created by Diamanti CSI driver to provide access to the storage.
Fire-drill support for DR
With 3.3.0 release Diamanti introduces support for fire-drill as part of its DR solution. A fire-drill is a zero-downtime DR test that mimics the failover behaviour of stateful applications across different sites. A successful fire-drill operation gives confidence that stateful applications failing over to the DR site will behave as expected when a real failure happens. With a single-click on Diamanti’s Spektra UI, a user is now able to create a new instance of the application on another Kubernetes cluster and verify the state of the data on the DR site. This is built on top of Diamanti’s snapshot feature that enables periodic snapshotting of application data from the primary to the secondary site. During the Fire-drill the original application remains untouched and continues to function with no downtime.
Route metric support for multi-endpoints PODs
With 3.3.0 release Diamanti introduces support for per-subnet default-route metric configuration when using multiple-endpoints for an application. Diamanti’s L2 CNI supports ability for applications to have multiple endpoints. This is especially useful for ingress-controllers where external traffic could be ingressing on one endpoint while getting routed into the cluster on another endpoint. Previously, user did not have control which interface inside the POD was used for the default route. With this feature, users now have full control over the default-route metric configuration through the POD spec. The default-route metric is an additional parameter that can be specified as part of the network-annotation inside the application spec and gets installed inside the POD through the Diamanti CNI.
KubeVirt:
KubeVirt technology addresses the needs of development teams that have adopted or want to adopt Kubernetes but are running workloads that are yet to be containerized. More specifically, this technology provides a unified development platform where developers can build, modify, and deploy applications residing in both Application Containers as well as Virtual Machines on a common, shared environment.
Diamanti’s network, storage and management features work seamlessly with KubeVirt. The VM failovers are also handled seamlessly in the 3.3.0 release.
