{"id":29793,"date":"2022-10-12T01:01:48","date_gmt":"2022-10-12T01:01:48","guid":{"rendered":"https:\/\/rbsitsoftwaresolution.com\/blog\/kata-containers-3s-marriage-of-virtual-machines-and-containers-continues.html"},"modified":"2022-10-12T01:01:48","modified_gmt":"2022-10-12T01:01:48","slug":"kata-containers-3s-marriage-of-virtual-machines-and-containers-continues","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/kata-containers-3s-marriage-of-virtual-machines-and-containers-continues.html","title":{"rendered":"Kata Containers 3’s marriage of virtual machines and containers continues"},"content":{"rendered":"
ZinetroN\/Shutterstock<\/span><\/figcaption><\/figure>\n

We use containers all the time, but we’re not ready to give up on Virtual Machines (VM) yet. Both have their uses. But, what if we could use the flexibility and ease of deployment of containers with the security and manageability of VMs?\u00a0 That’s the idea behind the OpenInfra Foundation’s<\/a> Kata Containers<\/a>, and it’s been fine-tuned in the latest release,\u00a0Kata Containers 3.0.0<\/a>.<\/p>\n

It started with the marriage of two different programs. The first was the Hyper.sh container platform<\/a>. This enabled containers to run in the runV container runtime<\/a>. It was then married to Intel’s Intel Clear Containers<\/a>, and their child is Kata Containers. Although it’s only five years old, Kata Containers has seen a lot of changes. The most important came with Kata 2.0.0., which migrated Kata to the Rust language.<\/a>\u00a0\u00a0<\/p>\n

The basic concept, however, remains the same.<\/p>\n

Also:<\/strong> StarlingX, the cloud for edge computing, gets a major upgrade<\/strong><\/a><\/p>\n

That is, Kata Containers provides a secure container runtime with lightweight VMs. These feel and act like containers but come with VM’s stronger workload isolation. It relies on AMD SVM and Intel VT-x CPU-based virtualization technology for this extra level of protection.\u00a0<\/p>\n

Kata Containers 3 also now has support for GPUs. This includes support for Virtual function I\/O (VFIO)<\/a>, which allows safe, non-privileged, user space drivers and PCIe devices.<\/p>\n

This version of Kata Containers also features a newly written Rust runtime implementation and an optional integrated Rust hypervisor. This makes the program even lighter and easier to manage.<\/p>\n

It all supports Kubernetes and container runtimes such as CRI-O, Containerd, cGroup v2, and OCI v1.0.0-rc5.\u00a0<\/p>\n

Underneath all this, Kata Containers has its own Linux kernel. The kernel in Kata Containers 3.0.0 is v5.19.2.<\/p>\n

Users are already happy with these new developments. As Treva Williams, OpenInfra’s technical community manager, said, “There’s a lot of excitement in the Kata Containers community around how the improved hypervisor support in Kata Containers 3.0.0 expands compatibility with a number of popular environment configurations and hardware technologies, such as GPUs.”<\/p>\n

In addition, a new project has sprung from Kata Containers. This is\u00a0Confidential Containers<\/a>, an open-source Cloud-Native Computing Foundation (CNCF) sandbox project. This outgrowth of Kata Containers’ container isolation, integrates Trusted Execution Environments (TEE)<\/a> infrastructure.\u00a0<\/p>\n

TEE is a hardware-based, trusted execution environment. With it, your application and data run in a secure and isolated environment. The alpha Confidential Containers 0.10 release can work with Kata 3.0.0. For more on this new project, see its GitHub Quickstart guide<\/a>.<\/p>\n

Article source: https:\/\/www.zdnet.com\/article\/kata-containers-3s-marriage-of-virtual-machines-and-containers-continues\/#ftag=RSSbaffb68<\/p>","protected":false},"excerpt":{"rendered":"

ZinetroN\/Shutterstock We use containers all the time, but we’re not ready to give up on Virtual Machines (VM) yet. Both have their uses. But, what if we could use the <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[31],"tags":[34],"class_list":["post-29793","post","type-post","status-publish","format-standard","hentry","category-linux-updates","tag-linux-updates"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t