base on Kubernetes Virtualization API and runtime in order to define and manage virtual machines. # KubeVirt <p align="center"> <img src="https://github.com/kubevirt/community/blob/main/logo/KubeVirt_icon.png" width="100"> </p> <div align="center"> [](https://prow.ci.kubevirt.io/?job=push-kubevirt-main) [](https://goreportcard.com/report/github.com/kubevirt/kubevirt) [](https://www.apache.org/licenses/LICENSE-2.0) [](https://coveralls.io/github/kubevirt/kubevirt?branch=main) [](https://bestpractices.coreinfrastructure.org/projects/3203) [](https://kubernetes.slack.com/?redir=%2Farchives%2FC0163DT0R8X) [](https://app.fossa.com/projects/custom%2B13072%2Fgit%40github.com%3Akubevirt%2Fkubevirt.git?ref=badge_shield) [](https://sonarcloud.io/summary/new_code?id=kubevirt_kubevirt) </div> **KubeVirt** is a virtual machine management add-on for Kubernetes. The aim is to provide a common ground for virtualization solutions on top of Kubernetes. ## Introduction ### Virtualization extension for Kubernetes At its core, KubeVirt extends [Kubernetes][k8s] by adding additional virtualization resource types (especially the `VM` type) through [Kubernetes's Custom Resource Definitions API][crd]. By using this mechanism, the Kubernetes API can be used to manage these `VM` resources alongside all other resources Kubernetes provides. The resources themselves are not enough to launch virtual machines. For this to happen the _functionality and business logic_ needs to be added to the cluster. The functionality is not added to Kubernetes itself, but rather added to a Kubernetes cluster by _running_ additional controllers and agents on an existing cluster. The necessary controllers and agents are provided by KubeVirt. As of today KubeVirt can be used to declaratively * Create a predefined VM * Schedule a VM on a Kubernetes cluster * Launch a VM * Stop a VM * Delete a VM [<img src="https://asciinema.org/a/497168.svg" width="50%">](https://asciinema.org/a/497168) ## To start using KubeVirt Try our quickstart at [kubevirt.io](https://kubevirt.io/get_kubevirt/). See our user documentation at [kubevirt.io/docs](https://kubevirt.io/user-guide). Once you have the basics, you can learn more about how to run KubeVirt and its newest features by taking a look at: * [KubeVirt blog](https://kubevirt.io/blogs/) * [KubeVirt Youtube channel](https://www.youtube.com/channel/UC2FH36TbZizw25pVT1P3C3g) ## To start developing KubeVirt To set up a development environment please read our [Getting Started Guide](docs/getting-started.md). To learn how to contribute, please read our [contribution guide](https://github.com/kubevirt/kubevirt/blob/main/CONTRIBUTING.md). You can learn more about how KubeVirt is designed (and why it is that way), and learn more about the major components by taking a look at [our developer documentation](docs/): * [Architecture](docs/architecture.md) - High-level view on the architecture * [Components](docs/components.md) - Detailed look at all components * [API Reference](https://kubevirt.io/api-reference/) ## Useful links The KubeVirt SIG-release repo is responsible for information regarding upcoming and previous releases. * [KubeVirt to Kubernetes version support matrix](https://github.com/kubevirt/sig-release/blob/main/releases/k8s-support-matrix.md) - Verify the versions of KubeVirt that are built and supported for your version of Kubernetes * [Noteworthy changes for the next KubeVirt release](https://github.com/kubevirt/sig-release/blob/main/upcoming-changes.md) - Pre-release notes for the upcoming release * [Release schedule](https://github.com/kubevirt/sig-release/blob/main/releases/) - For our current and previous releases ## Community If you got enough of code and want to speak to people, then you got a couple of options: * Follow us on [Twitter](https://twitter.com/kubevirt) * Chat with us on Slack via [#virtualization @ kubernetes.slack.com](https://kubernetes.slack.com/?redir=%2Farchives%2FC8ED7RKFE) * Discuss with us on the [kubevirt-dev Google Group](https://groups.google.com/forum/#!forum/kubevirt-dev) * Stay informed about designs and upcoming events by watching our [community content](https://github.com/kubevirt/community/) ### Related resources * [Kubernetes][k8s] * [Libvirt][libvirt] * [Cockpit][cockpit] * [Kubevirt-ansible][kubevirt-ansible] ### Submitting patches When sending patches to the project, the submitter is required to certify that they have the legal right to submit the code. This is achieved by adding a line Signed-off-by: Real Name <[email protected]> to the bottom of every commit message. Existence of such a line certifies that the submitter has complied with the Developer's Certificate of Origin 1.1, (as defined in the file docs/developer-certificate-of-origin). This line can be automatically added to a commit in the correct format, by using the '-s' option to 'git commit'. ## License KubeVirt is distributed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt). Copyright 2016 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. [//]: # (Reference links) [k8s]: https://kubernetes.io [crd]: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ [ovirt]: https://www.ovirt.org [cockpit]: https://cockpit-project.org/ [libvirt]: https://www.libvirt.org [kubevirt-ansible]: https://github.com/kubevirt/kubevirt-ansible ## FOSSA Status [](https://app.fossa.com/projects/custom%2B13072%2Fgit%40github.com%3Akubevirt%2Fkubevirt.git?ref=badge_large) ", Assign "at most 3 tags" to the expected json: {"id":"1421","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"