<commit_before>---
layout: guides
title: Using Weave with Kubernetes on a CoreOS Cluster
description: Using a weave network with Kubernetes on CoreOS
tags: kubernetes, php, ipam, coreos cluster
permalink: /guides/kubernetes/coreos/weave-kubernetes-coreos.html

shorttitle: Weave and Kubernetes on CoreOS
sidebarpath: /start/kubernetes
sidebarweight: 60
---

## What You Will Build

Kubernetes is an open source container cluster manager built by Google. It allows you to manage multiple clusters spread across multiple machines. With Kubernetes there is the concept of the pod, which represents a collection of containers deployed as a single logical unit. For more information see the [Kubernetes Overview](http://kubernetes.io/v1.0/docs/user-guide/overview.html)

In this example, we will demonstrate how you can use a Weave network with Kubernetes on a CoreOS cluster. Although there are other network fabric solutions such as [Flannel](https://coreos.com/flannel/docs/latest/flannel-config.html) and [Calico](http://www.projectcalico.org/), only Weave provides simple to deploy [encryption](http://docs.weave.works/weave/latest_release/features.html#security) and automatic unique IP assigment using [IPAM](http://docs.weave.works/weave/latest_release/features.html#addressing). Weave furthermore, is one of the few solutions that can monitor any uncontainerized services that you may have, such as legacy databases, together on a container network. 

This is a reworked version of our old Kubernetes guide. Many new features have been added to Weave since the time of writing. Both Weave and Kubernetes have become much more mature as they've gone beyond 1.0 releases.

With the [Weave 1.1 release](https://github.com/weaveworks/weave/releases) users can utilise a Docker API proxy and IP address allocation with Kubernetes, thereby removing the need to configure the Docker daemon with statically allocated subnets for each host.
<commit_msg>Match URL path with Mesos guide<commit_after>---
layout: guides
title: Using Weave with Kubernetes on a CoreOS Cluster
description: Using a weave network with Kubernetes on CoreOS
tags: kubernetes, php, ipam, coreos cluster
permalink: /guides/platform/kubernetes/os/coreos/cloud/vagrant/index.html

shorttitle: Weave and Kubernetes on CoreOS
sidebarpath: /start/kubernetes
sidebarweight: 60
---

## What You Will Build

Kubernetes is an open source container cluster manager built by Google. It allows you to manage multiple clusters spread across multiple machines. With Kubernetes there is the concept of the pod, which represents a collection of containers deployed as a single logical unit. For more information see the [Kubernetes Overview](http://kubernetes.io/v1.0/docs/user-guide/overview.html)

In this example, we will demonstrate how you can use a Weave network with Kubernetes on a CoreOS cluster. Although there are other network fabric solutions such as [Flannel](https://coreos.com/flannel/docs/latest/flannel-config.html) and [Calico](http://www.projectcalico.org/), only Weave provides simple to deploy [encryption](http://docs.weave.works/weave/latest_release/features.html#security) and automatic unique IP assigment using [IPAM](http://docs.weave.works/weave/latest_release/features.html#addressing). Weave furthermore, is one of the few solutions that can monitor any uncontainerized services that you may have, such as legacy databases, together on a container network. 

This is a reworked version of our old Kubernetes guide. Many new features have been added to Weave since the time of writing. Both Weave and Kubernetes have become much more mature as they've gone beyond 1.0 releases.

With the [Weave 1.1 release](https://github.com/weaveworks/weave/releases) users can utilise a Docker API proxy and IP address allocation with Kubernetes, thereby removing the need to configure the Docker daemon with statically allocated subnets for each host.

{'fraction_non_alphanumeric': 0.06629270780214176, 'fraction_numerical': 0.00407955124936257, 'mean_word_length': 5.072755417956657, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1178491', 'n_tokens_mistral': 1032, 'n_tokens_neox': 970, 'n_words': 479}