-
Notifications
You must be signed in to change notification settings - Fork 117
/
index.html
73 lines (66 loc) · 3.5 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
---
layout: homepage
---
<section class="kv-why">
<h2>Why KubeVirt?</h2>
<p>
KubeVirt technology addresses the needs of development teams that have adopted or want to adopt <a href="https://kubernetes.io/">Kubernetes</a> but
possess existing Virtual Machine-based workloads that cannot be easily containerized. More specifically, the
technology provides a unified development platform where developers can build, modify, and deploy applications
residing in both Application Containers as well as Virtual Machines in a common, shared environment.
</p>
<p>
Benefits are broad and significant. Teams with a reliance on existing virtual machine-based workloads are
empowered to rapidly containerize applications. With virtualized workloads placed directly in development workflows,
teams can decompose them over time while still leveraging remaining virtualized components as is comfortably desired.
</p>
<!-- <img src="./../assets/images/home-image1.svg" width="300px" height="300px" alt="Workload Balancing"> -->
</section>
<section class="kv-what">
<h2 class="kv-what__title">What can I do with KubeVirt?</h2>
<img class="kv-what__img" src="./../assets/images/home-image-col1.svg" alt="KubeVirt and Kubernetes">
<p class="kv-what__text">Leverage KubeVirt and Kubernetes to manage virtual machines for impractical-to-containerize apps.</p>
<img class="kv-what__img" src="./../assets/images/home-image-col2.svg" alt="KubeVirt and VMs">
<p class="kv-what__text">Combine existing virtualized workloads with new container workloads on the one platform.</p>
<img class="kv-what__img" src="./../assets/images/home-image-col3.svg" alt="Containerized Applications">
<p class="kv-what__text">Support development of new microservice applications in containers that interact with existing virtualized applications.</p>
</section>
<section class="kv-recent-posts">
<h2>Recent posts</h2>
{% for post in site.posts limit:7 %}
<article class="kv-blog__snippet">
<a href="{{ post.url }}" class="kv-blog__snippet__link">
<h4 class="">{{ post.title }}</h4>
<time datetime="1999-12-23" class="">{{ post.date | date: "%a, %-d/%m/%y" }}</time>
</a>
</article>
{% endfor %}
</section>
<br>
<section class="kv-endusers">
<h2 class="kv-what__title">End Users</h2>
<p>
{% for enduser in site.data.adopters.adopters.endusers %}
<a href="{{ enduser.link }}" class="kv-endusers" data-toggle="tooltip" data-placement="top" title="{{ enduser.name }}">
<img src="./../assets/images/adopters/{{ enduser.logo }}" alt="{{ enduser.name }}">
</a>
{% endfor %}</p>
</section>
<section class="kv-vendors">
<h2 class="kv-what__title">Vendors</h2>
<p>
{% for vendors in site.data.adopters.adopters.vendors %}
<a href="{{ vendors.link }}" class="kv-vendors" data-toggle="tooltip" data-placement="top" title="{{ vendors.name }}">
<img src="./../assets/images/adopters/{{ vendors.logo }}" alt="{{ vendors.name }}">
</a>
{% endfor %}</p>
</section>
<section class="kv-integrations">
<h2 class="kv-what__title">Integrations</h2>
<p>
{% for integrations in site.data.adopters.adopters.integrations %}
<a href="{{ integrations.link }}" class="kv-integrations" data-toggle="tooltip" data-placement="top" title="{{ integrations.name }}">
<img src="./../assets/images/adopters/{{ integrations.logo }}" alt="{{ integrations.name }}">
</a>
{% endfor %}</p>
</section>