Kubernetes Cluster API Provider Kubevirt

Kubernetes-native declarative infrastructure for Kubevirt.

What is the Cluster API Provider Kubevirt?

The Cluster API brings declarative Kubernetes-style APIs to cluster creation, configuration and management. The API itself is shared across multiple cloud providers allowing for true Kubevirt hybrid deployments of Kubernetes.

Quick Start

Checkout our Cluster API Quick Start to create your first Kubernetes cluster.

Getting Involved and Contributing

Are you interested in contributing to cluster-api-provider-kubevirt? We, the maintainers and the community, would love your suggestions, support and contributions! The maintainers of the project can be contacted anytime to learn about how to get involved.

In the interest of getting new people involved have issues marked as good-first-issues. Although the issues have a smaller scope but are very helpful in getting accquintated with the codebase. For more see the issue tracker. If you're unsure where to start, feel free to reach out to discuss.

See also: Our own contributor guide and the Kubernetes community page.

We also encourage ALL active community participants to act as if they are maintainers, even if you don't have 'official' written permissions. This is a community effort and we are here to serve the Kubernetes community. If you have an active interest and you want to get involved, you have real power!

Office hours

• Join the SIG Cluster Lifecycle Google Group to documents and calendar.

• Participate in the conversations on Kubernetes Discuss

• Meetings:

  • Cluster API Provider KubeVirt Syncup Meetings: Tuesdays at 8:00 PT (Pacific Time) (weekly starting Tuesday, December 7th, 2021). Convert to your timezone.
    • Meeting notes and Agenda.

Other ways to communicate with the maintainers

Please check in with us in the #cluster-api-kubevirt. You can also join our Mailing List

Github Issues

Bugs

If you think you have found a bug please follow the instruction below.

• Please give a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
• Get the logs from the custom controllers and please paste them in the issue.
• Open a bug report.
• Remember users might be searching the issue in the future, so please make sure to give it a meaningful title to help others.
• Feel free to reach out to the community on slack.

Tracking new feature

We also have an issue tracker to track features. If you think you have a feature idea, that could make Cluster API provider Kubevirt become even more awesome, then follow these steps.

• Open a feature request
• Remember users might be searching for the issue in the future, so please make sure to give it a meaningful title to help others.
• Clearly define the use case with concrete examples. Example: type this and cluster-api-provider-kubevirt does that.
• Some of our larger features will require some design. If you would like to include a technical design to your feature, please go ahead.
• After the new feature is well understood, and the design is agreed upon we can start coding the feature. We would love for you to code it. So please open up a WIP (work in progress) PR and happy coding!

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.