mirror of https://github.com/k3s-io/k3s
4f1fe55a9e
|
||
|---|---|---|
| .. | ||
| aws | ||
| centos | ||
| coreos | ||
| docker-multinode | ||
| fedora | ||
| mesos | ||
| README.md | ||
| aws-coreos.md | ||
| aws.md | ||
| azure.md | ||
| binary_release.md | ||
| cloudstack.md | ||
| coreos.md | ||
| docker-multinode.md | ||
| docker.md | ||
| gce.md | ||
| juju.md | ||
| k8s-docker.png | ||
| k8s-singlenode-docker.png | ||
| libvirt-coreos.md | ||
| locally.md | ||
| logging.md | ||
| mesos.md | ||
| ovirt.md | ||
| rackspace.md | ||
| ubuntu.md | ||
| vagrant.md | ||
| vsphere.md | ||
README.md
If you are not sure what OSes and infrastructure is supported, the table below lists all the combinations which have been tested recently.
For the easiest "kick the tires" experience, please try the local docker guide.
If you are considering contributing a new guide, please read the guidelines.
| IaaS Provider | Config. Mgmt | OS | Networking | Docs | Support Level | Notes |
|---|---|---|---|---|---|---|
| GKE | GCE | docs | Commercial | Uses K8s version 0.15.0 | ||
| Vagrant | Saltstack | Fedora | OVS | docs | Project | Uses latest via https://get.k8s.io/ |
| GCE | Saltstack | Debian | GCE | docs | Project | Tested with 0.15.0 by @robertbailey |
| Azure | CoreOS | CoreOS | Weave | docs | Community (@errordeveloper, @squillace, @chanezon, @crossorigin) | Uses K8s version 0.15.0 |
| Docker Single Node | custom | N/A | local | docs | Project (@brendandburns) | Tested @ 0.14.1 |
| Docker Multi Node | Flannel | N/A | local | docs | Project (@brendandburns) | Tested @ 0.14.1 |
| Bare-metal | Ansible | Fedora | flannel | docs | Project | Uses K8s v0.13.2 |
| Bare-metal | custom | Fedora | none | docs | Project | Uses K8s v0.13.2 |
| Bare-metal | custom | Fedora | flannel | docs | Community (@aveshagarwal) | Tested with 0.15.0 |
| libvirt | custom | Fedora | flannel | docs | Community (@aveshagarwal) | Tested with 0.15.0 |
| KVM | custom | Fedora | flannel | docs | Community (@aveshagarwal) | Tested with 0.15.0 |
| Mesos/GCE | docs | Community (@jdef) | Uses K8s v0.11.2 | |||
| AWS | CoreOS | CoreOS | flannel | docs | Community | Uses K8s version 0.17.0 |
| GCE | CoreOS | CoreOS | flannel | docs | Community (@kelseyhightower) | Uses K8s version 0.15.0 |
| Vagrant | CoreOS | CoreOS | flannel | docs | Community ( @pires, @AntonioMeireles ) | Uses K8s version 0.15.0 |
| Bare-metal (Offline) | CoreOS | CoreOS | flannel | docs | Community(@jeffbean) | Uses K8s version 0.15.0 |
| CloudStack | Ansible | CoreOS | flannel | docs | Community (@runseb) | Uses K8s version 0.9.1 |
| Vmware | Debian | OVS | docs | Community (@pietern) | Uses K8s version 0.9.1 | |
| Bare-metal | custom | CentOS | none | docs | Community(@coolsvap) | Uses K8s v0.9.1 |
| AWS | Juju | Ubuntu | flannel | docs | Community ( @whit, @matt, @chuck ) | Tested K8s v0.8.1 |
| OpenStack/HPCloud | Juju | Ubuntu | flannel | docs | Community ( @whit, @matt, @chuck ) | Tested K8s v0.8.1 |
| Joyent | Juju | Ubuntu | flannel | docs | Community ( @whit, @matt, @chuck ) | Tested K8s v0.8.1 |
| AWS | Saltstack | Ubuntu | OVS | docs | Community (@justinsb) | Uses K8s version 0.5.0 |
| Vmware | CoreOS | CoreOS | flannel | docs | Community (@kelseyhightower) | Uses K8s version 0.15.0 |
| Azure | Saltstack | Ubuntu | OpenVPN | docs | Community | |
| Bare-metal | custom | Ubuntu | flannel | docs | Community (@resouer @WIZARD-CXY) | use k8s version 0.15.0 |
| Docker Single Node | custom | N/A | local | docs | Project (@brendandburns) | Tested @ 0.14.1 |
| Docker Multi Node | Flannel | N/A | local | docs | Project (@brendandburns) | Tested @ 0.14.1 |
| Local | none | docs | Community (@preillyme) | |||
| libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | docs | Community (@lhuard1A) | |
| oVirt | docs | Community (@simon3z) |
Note: The above table is ordered by version test/used in notes followed by support level.
Definition of columns:
- IaaS Provider is who/what provides the virtual or physical machines (nodes) that Kubernetes runs on.
- OS is the base operating system of the nodes.
- Config. Mgmt is the configuration management system that helps install and maintain kubernetes software on the nodes.
- Networking is what implements the networking model. Those with networking type none may not support more than one node, or may support multiple VM nodes only in the same physical node.
- Support Levels
- Project: Kubernetes Committers regularly use this configuration, so it usually works with the latest release of Kubernetes.
- Commercial: A commercial offering with its own support arrangements.
- Community: Actively supported by community contributions. May not work with more recent releases of kubernetes.
- Inactive: No active maintainer. Not recommended for first-time K8s users, and may be deleted soon.
- Notes is relevant information such as version k8s used.