Quickstarts and Running Kubernetes rough pass
This commit is contained in:
John Mulhausen
@@ -1,37 +1,16 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Creating a Kubernetes Cluster"
|
||||
title: "Picking the Right Solution"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
Creating a Kubernetes Cluster
|
||||
----------------------------------------
|
||||
|
||||
Kubernetes can run on a range of platforms, from your laptop, to VMs on a cloud provider, to rack of
|
||||
bare metal servers. The effort required to set up a cluster varies from running a single command to
|
||||
crafting your own customized cluster. We'll guide you in picking a solution that fits for your needs.
|
||||
|
||||
**Table of Contents**
|
||||
<!-- BEGIN MUNGE: GENERATED_TOC -->
|
||||
## Table of Contents
|
||||
|
||||
- [Picking the Right Solution](#picking-the-right-solution)
|
||||
- [Local-machine Solutions](#local-machine-solutions)
|
||||
- [Hosted Solutions](#hosted-solutions)
|
||||
- [Turn-key Cloud Solutions](#turn-key-cloud-solutions)
|
||||
- [Custom Solutions](#custom-solutions)
|
||||
- [Cloud](#cloud)
|
||||
- [On-Premises VMs](#on-premises-vms)
|
||||
- [Bare Metal](#bare-metal)
|
||||
- [Integrations](#integrations)
|
||||
- [Table of Solutions](#table-of-solutions)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
<!-- END MUNGE: GENERATED_TOC -->
|
||||
|
||||
|
||||
## Picking the Right Solution
|
||||
## Options
|
||||
|
||||
If you just want to "kick the tires" on Kubernetes, we recommend the [local Docker-based](docker.html) solution.
|
||||
|
||||
@@ -199,17 +178,4 @@ Definition of columns:
|
||||
<!-- Vagrant conformance test result -->
|
||||
[2]: https://gist.github.com/derekwaynecarr/505e56036cdf010bf6b6
|
||||
<!-- GKE conformance test result -->
|
||||
[3]: https://gist.github.com/erictune/2f39b22f72565365e59b
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
[3]: https://gist.github.com/erictune/2f39b22f72565365e59b
|
||||
@@ -1,25 +1,10 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on AWS EC2"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
## Table of Contents
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on AWS EC2
|
||||
--------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Cluster turnup](#cluster-turnup)
|
||||
- [Supported procedure: `get-kube`](#supported-procedure-get-kube)
|
||||
- [Alternatives](#alternatives)
|
||||
- [Getting started with your cluster](#getting-started-with-your-cluster)
|
||||
- [Command line administration tool: `kubectl`](#command-line-administration-tool-kubectl)
|
||||
- [Examples](#examples)
|
||||
- [Tearing down the cluster](#tearing-down-the-cluster)
|
||||
- [Further reading](#further-reading)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@@ -1,18 +1,10 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on CentOS"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
## Table of Contents
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on [CentOS](http://centos.org)
|
||||
----------------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Starting a cluster](#starting-a-cluster)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -204,17 +196,4 @@ centos-minion <none> Ready
|
||||
|
||||
**The cluster should be running! Launch a test pod.**
|
||||
|
||||
You should have a functional cluster, check out [101](../../../docs/user-guide/walkthrough/README.html)!
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
You should have a functional cluster, check out [101](../../../docs/user-guide/walkthrough/README.html)!
|
||||
@@ -1,22 +1,9 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on CloudStack"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on [CloudStack](http://cloudstack.apache.org)
|
||||
------------------------------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Clone the playbook](#clone-the-playbook)
|
||||
- [Create a Kubernetes cluster](#create-a-kubernetes-cluster)
|
||||
|
||||
### Introduction
|
||||
## Introduction
|
||||
|
||||
CloudStack is a software to build public and private clouds based on hardware virtualization principles (traditional IaaS). To deploy Kubernetes on CloudStack there are several possibilities depending on the Cloud being used and what images are made available. [Exoscale](http://exoscale.ch) for instance makes a [CoreOS](http://coreos.com) template available, therefore instructions to deploy Kubernetes on coreOS can be used. CloudStack also has a vagrant plugin available, hence Vagrant could be used to deploy Kubernetes either using the existing shell provisioner or using new Salt based recipes.
|
||||
|
||||
@@ -28,7 +15,11 @@ This is a completely automated, a single playbook deploys Kubernetes based on th
|
||||
|
||||
This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.
|
||||
|
||||
### Prerequisites
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
$ sudo apt-get install -y python-pip
|
||||
$ sudo pip install ansible
|
||||
@@ -89,17 +80,4 @@ SSH to it using the key that was created and using the _core_ user and you can l
|
||||
MACHINE IP METADATA
|
||||
a017c422... <node #1 IP> role=node
|
||||
ad13bf84... <master IP> role=master
|
||||
e9af8293... <node #2 IP> role=node
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
e9af8293... <node #2 IP> role=node
|
||||
@@ -1,13 +1,11 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting Started on CoreOS"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
## Table of Contents
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
## Getting Started on [CoreOS](https://coreos.com)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
There are multiple guides on running Kubernetes with [CoreOS](https://coreos.com/kubernetes/docs/latest/):
|
||||
|
||||
@@ -73,16 +71,4 @@ Guide to running an HA etcd cluster with a single master on Azure. Uses the Azur
|
||||
|
||||
[**Multi-node cluster using cloud-config, CoreOS and VMware ESXi**](https://github.com/xavierbaude/VMware-coreos-multi-nodes-Kubernetes)
|
||||
|
||||
Configure a single master, single worker cluster on VMware ESXi.
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
Configure a single master, single worker cluster on VMware ESXi.
|
||||
@@ -1,29 +1,16 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Kubernetes on Azure with CoreOS and Weave"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Kubernetes on Azure with CoreOS and [Weave](http://weave.works)
|
||||
---------------------------------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Let's go!](#lets-go)
|
||||
- [Deploying the workload](#deploying-the-workload)
|
||||
- [Scaling](#scaling)
|
||||
- [Exposing the app to the outside world](#exposing-the-app-to-the-outside-world)
|
||||
- [Next steps](#next-steps)
|
||||
- [Tear down...](#tear-down)
|
||||
|
||||
## Introduction
|
||||
|
||||
In this guide I will demonstrate how to deploy a Kubernetes cluster to Azure cloud. You will be using CoreOS with Weave, which implements simple and secure networking, in a transparent, yet robust way. The purpose of this guide is to provide an out-of-the-box implementation that can ultimately be taken into production with little change. It will demonstrate how to provision a dedicated Kubernetes master and etcd nodes, and show how to scale the cluster with ease.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Prerequisites
|
||||
|
||||
1. You need an Azure account.
|
||||
@@ -273,17 +260,4 @@ If you don't wish care about the Azure bill, you can tear down the cluster. It's
|
||||
|
||||
> Note: make sure to use the _latest state file_, as after scaling there is a new one.
|
||||
|
||||
By the way, with the scripts shown, you can deploy multiple clusters, if you like :)
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
By the way, with the scripts shown, you can deploy multiple clusters, if you like :)
|
||||
@@ -1,32 +1,12 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Bare Metal CoreOS with Kubernetes (OFFLINE)"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Bare Metal CoreOS with Kubernetes (OFFLINE)
|
||||
------------------------------------------
|
||||
Deploy a CoreOS running Kubernetes environment. This particular guild is made to help those in an OFFLINE system, wither for testing a POC before the real deal, or you are restricted to be totally offline for your applications.
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [High Level Design](#high-level-design)
|
||||
- [This Guides variables](#this-guides-variables)
|
||||
- [Setup PXELINUX CentOS](#setup-pxelinux-centos)
|
||||
- [Adding CoreOS to PXE](#adding-coreos-to-pxe)
|
||||
- [DHCP configuration](#dhcp-configuration)
|
||||
- [Kubernetes](#kubernetes)
|
||||
- [Cloud Configs](#cloud-configs)
|
||||
- [master.yml](#masteryml)
|
||||
- [node.yml](#nodeyml)
|
||||
- [New pxelinux.cfg file](#new-pxelinuxcfg-file)
|
||||
- [Specify the pxelinux targets](#specify-the-pxelinux-targets)
|
||||
- [Creating test pod](#creating-test-pod)
|
||||
- [Helping commands for debugging](#helping-commands-for-debugging)
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -675,17 +655,4 @@ List Kubernetes
|
||||
|
||||
Kill all pods:
|
||||
|
||||
for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done
|
||||
@@ -1,13 +1,7 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Running Multi-Node Kubernetes Using Docker"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Running Multi-Node Kubernetes Using Docker
|
||||
------------------------------------------
|
||||
|
||||
_Note_:
|
||||
These instructions are somewhat significantly more advanced than the [single node](docker.html) instructions. If you are
|
||||
@@ -17,15 +11,9 @@ _Note_:
|
||||
There is a [bug](https://github.com/docker/docker/issues/14106) in Docker 1.7.0 that prevents this from working correctly.
|
||||
Please install Docker 1.6.2 or Docker 1.7.1.
|
||||
|
||||
**Table of Contents**
|
||||
## Table of Contents
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Overview](#overview)
|
||||
- [Bootstrap Docker](#bootstrap-docker)
|
||||
- [Master Node](#master-node)
|
||||
- [Adding a worker node](#adding-a-worker-node)
|
||||
- [Deploy a DNS](#deploy-a-dns)
|
||||
- [Testing your cluster](#testing-your-cluster)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -103,17 +91,4 @@ See [here](docker-multinode/deployDNS.html) for instructions.
|
||||
|
||||
Once your cluster has been created you can [test it out](docker-multinode/testing.html)
|
||||
|
||||
For more complete applications, please look in the [examples directory](../../examples/)
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
For more complete applications, please look in the [examples directory](../../examples/)
|
||||
@@ -1,25 +1,11 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Running Kubernetes locally via Docker"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
## Table of Contents
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Running Kubernetes locally via Docker
|
||||
-------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Overview](#setting-up-a-cluster)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Step One: Run etcd](#step-one-run-etcd)
|
||||
- [Step Two: Run the master](#step-two-run-the-master)
|
||||
- [Step Three: Run the service proxy](#step-three-run-the-service-proxy)
|
||||
- [Test it out](#test-it-out)
|
||||
- [Run an application](#run-an-application)
|
||||
- [Expose it as a service](#expose-it-as-a-service)
|
||||
- [A note on turning down your cluster](#a-note-on-turning-down-your-cluster)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Overview
|
||||
|
||||
@@ -187,16 +173,4 @@ Note that you will need run this curl command on your boot2docker VM if you are
|
||||
Many of these containers run under the management of the `kubelet` binary, which attempts to keep containers running, even if they fail. So, in order to turn down
|
||||
the cluster, you need to first kill the kubelet container, and then any other containers.
|
||||
|
||||
You may use `docker kill $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution.
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
You may use `docker kill $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution.
|
||||
@@ -1,23 +1,13 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Configuring Kubernetes on Fedora via Ansible"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Configuring Kubernetes on [Fedora](http://fedoraproject.org) via [Ansible](http://www.ansible.com/home)
|
||||
-------------------------------------------------------------------------------------------------------
|
||||
|
||||
Configuring Kubernetes on Fedora via Ansible offers a simple way to quickly create a clustered environment with little effort.
|
||||
|
||||
**Table of Contents**
|
||||
## Table of Contents
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Architecture of the cluster](#architecture-of-the-cluster)
|
||||
- [Setting up ansible access to your nodes](#setting-up-ansible-access-to-your-nodes)
|
||||
- [Setting up the cluster](#setting-up-the-cluster)
|
||||
- [Testing and using your new cluster](#testing-and-using-your-new-cluster)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -277,17 +267,4 @@ curl http://localhost
|
||||
{% endraw %}
|
||||
{% endhighlight %}
|
||||
|
||||
That's it !
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
That's it !
|
||||
@@ -2,20 +2,9 @@
|
||||
layout: docwithnav
|
||||
title: "Kubernetes multiple nodes cluster with flannel on Fedora"
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
## Table of Contents
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Kubernetes multiple nodes cluster with flannel on Fedora
|
||||
--------------------------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Master Setup](#master-setup)
|
||||
- [Node Setup](#node-setup)
|
||||
- [**Test the cluster and flannel configuration**](#test-the-cluster-and-flannel-configuration)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -219,17 +208,4 @@ PING 18.16.90.4 (18.16.90.4) 56(84) bytes of data.
|
||||
{% endraw %}
|
||||
{% endhighlight %}
|
||||
|
||||
* Now Kubernetes multi-node cluster is set up with overlay networking set up by flannel.
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
* Now Kubernetes multi-node cluster is set up with overlay networking set up by flannel.
|
||||
@@ -1,34 +1,14 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on Google Compute Engine"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on Google Compute Engine
|
||||
----------------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Before you start](#before-you-start)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Starting a cluster](#starting-a-cluster)
|
||||
- [Installing the Kubernetes command line tools on your workstation](#installing-the-kubernetes-command-line-tools-on-your-workstation)
|
||||
- [Getting started with your cluster](#getting-started-with-your-cluster)
|
||||
- [Inspect your cluster](#inspect-your-cluster)
|
||||
- [Run some examples](#run-some-examples)
|
||||
- [Tearing down the cluster](#tearing-down-the-cluster)
|
||||
- [Customizing](#customizing)
|
||||
- [Troubleshooting](#troubleshooting)
|
||||
- [Project settings](#project-settings)
|
||||
- [Cluster initialization hang](#cluster-initialization-hang)
|
||||
- [SSH](#ssh)
|
||||
- [Networking](#networking)
|
||||
|
||||
|
||||
The example below creates a Kubernetes cluster with 4 worker node Virtual Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This cluster is set up and controlled from your workstation (or wherever you find convenient).
|
||||
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Before you start
|
||||
|
||||
If you want a simplified getting started experience and GUI for managing clusters, please consider trying [Google Container Engine](https://cloud.google.com/container-engine/) (GKE) for hosted cluster installation and management.
|
||||
@@ -257,17 +237,4 @@ being used in `cluster/config-default.sh` create a new rule with the following
|
||||
field values:
|
||||
|
||||
* Source Ranges: `10.0.0.0/8`
|
||||
* Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp`
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
* Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp`
|
||||
@@ -1,35 +1,15 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started with Juju"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
Getting started with Juju
|
||||
-------------------------
|
||||
|
||||
[Juju](https://jujucharms.com/docs/stable/about-juju) makes it easy to deploy
|
||||
Kubernetes by provisioning, installing and configuring all the systems in
|
||||
the cluster. Once deployed the cluster can easily scale up with one command
|
||||
to increase the cluster size.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [On Ubuntu](#on-ubuntu)
|
||||
- [With Docker](#with-docker)
|
||||
- [Launch Kubernetes cluster](#launch-kubernetes-cluster)
|
||||
- [Exploring the cluster](#exploring-the-cluster)
|
||||
- [Run some containers!](#run-some-containers)
|
||||
- [Scale out cluster](#scale-out-cluster)
|
||||
- [Launch the "k8petstore" example app](#launch-the-k8petstore-example-app)
|
||||
- [Tear down cluster](#tear-down-cluster)
|
||||
- [More Info](#more-info)
|
||||
- [Cloud compatibility](#cloud-compatibility)
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -243,17 +223,4 @@ If you do not see your favorite cloud provider listed many clouds can be
|
||||
configured for [manual provisioning](https://jujucharms.com/docs/stable/config-manual).
|
||||
|
||||
The Kubernetes bundle has been tested on GCE and AWS and found to work with
|
||||
version 1.0.0.
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
version 1.0.0.
|
||||
@@ -1,27 +1,10 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started with libvirt CoreOS"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
## Table of Contents
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started with libvirt CoreOS
|
||||
-----------------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Highlights](#highlights)
|
||||
- [Warnings about `libvirt-coreos` use case](#warnings-about-libvirt-coreos-use-case)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Setup](#setup)
|
||||
- [Interacting with your Kubernetes cluster with the `kube-*` scripts.](#interacting-with-your-kubernetes-cluster-with-the-kube--scripts)
|
||||
- [Troubleshooting](#troubleshooting)
|
||||
- [!!! Cannot find kubernetes-server-linux-amd64.tar.gz](#-cannot-find-kubernetes-server-linux-amd64targz)
|
||||
- [Can't find virsh in PATH, please fix and retry.](#cant-find-virsh-in-path-please-fix-and-retry)
|
||||
- [error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory](#error-failed-to-connect-socket-to-varrunlibvirtlibvirt-sock-no-such-file-or-directory)
|
||||
- [error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied](#error-failed-to-connect-socket-to-varrunlibvirtlibvirt-sock-permission-denied)
|
||||
- [error: Out of memory initializing network (virsh net-create...)](#error-out-of-memory-initializing-network-virsh-net-create)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Highlights
|
||||
|
||||
@@ -350,17 +333,4 @@ usermod -a -G libvirtd $USER
|
||||
|
||||
#### error: Out of memory initializing network (virsh net-create...)
|
||||
|
||||
Ensure libvirtd has been restarted since ebtables was installed.
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
Ensure libvirtd has been restarted since ebtables was installed.
|
||||
@@ -1,20 +1,10 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on oVirt"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
## Table of Contents
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on oVirt
|
||||
------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [What is oVirt](#what-is-ovirt)
|
||||
- [oVirt Cloud Provider Deployment](#ovirt-cloud-provider-deployment)
|
||||
- [Using the oVirt Cloud Provider](#using-the-ovirt-cloud-provider)
|
||||
- [oVirt Cloud Provider Screencast](#ovirt-cloud-provider-screencast)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## What is oVirt
|
||||
|
||||
@@ -59,17 +49,4 @@ The `ovirt-cloud.conf` file then must be specified in kube-controller-manager:
|
||||
|
||||
This short screencast demonstrates how the oVirt Cloud Provider can be used to dynamically add VMs to your Kubernetes cluster.
|
||||
|
||||
[](http://www.youtube.com/watch?v=JyyST4ZKne8)
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
[](http://www.youtube.com/watch?v=JyyST4ZKne8)
|
||||
@@ -1,23 +1,7 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started on Rackspace"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started on Rackspace
|
||||
----------------------------
|
||||
|
||||
**Table of Contents**
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Provider: Rackspace](#provider-rackspace)
|
||||
- [Build](#build)
|
||||
- [Cluster](#cluster)
|
||||
- [Some notes:](#some-notes)
|
||||
- [Network Design](#network-design)
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -33,6 +17,10 @@ The current cluster design is inspired by:
|
||||
- [corekube](https://github.com/metral/corekube)
|
||||
- [Angus Lees](https://github.com/anguslees/kube-openstack)
|
||||
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. Python2.7
|
||||
@@ -76,17 +64,4 @@ There is a specific `cluster/rackspace` directory with the scripts for the follo
|
||||
|
||||
- eth0 - Public Interface used for servers/containers to reach the internet
|
||||
- eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc) communicate via this interface. The `cloud-config` files use the special CoreOS identifier `$private_ipv4` to configure the services.
|
||||
- eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
- eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.
|
||||
@@ -1,13 +1,7 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started from Scratch"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started from Scratch
|
||||
----------------------------
|
||||
|
||||
This guide is for people who want to craft a custom Kubernetes cluster. If you
|
||||
can find an existing Getting Started Guide that meets your needs on [this
|
||||
@@ -21,50 +15,9 @@ pre-defined guides.
|
||||
This guide is also useful for those wanting to understand at a high level some of the
|
||||
steps that existing cluster setup scripts are making.
|
||||
|
||||
**Table of Contents**
|
||||
## Table of Contents
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_TOC -->
|
||||
|
||||
- [Designing and Preparing](#designing-and-preparing)
|
||||
- [Learning](#learning)
|
||||
- [Cloud Provider](#cloud-provider)
|
||||
- [Nodes](#nodes)
|
||||
- [Network](#network)
|
||||
- [Cluster Naming](#cluster-naming)
|
||||
- [Software Binaries](#software-binaries)
|
||||
- [Downloading and Extracting Kubernetes Binaries](#downloading-and-extracting-kubernetes-binaries)
|
||||
- [Selecting Images](#selecting-images)
|
||||
- [Security Models](#security-models)
|
||||
- [Preparing Certs](#preparing-certs)
|
||||
- [Preparing Credentials](#preparing-credentials)
|
||||
- [Configuring and Installing Base Software on Nodes](#configuring-and-installing-base-software-on-nodes)
|
||||
- [Docker](#docker)
|
||||
- [rkt](#rkt)
|
||||
- [kubelet](#kubelet)
|
||||
- [kube-proxy](#kube-proxy)
|
||||
- [Networking](#networking)
|
||||
- [Other](#other)
|
||||
- [Using Configuration Management](#using-configuration-management)
|
||||
- [Bootstrapping the Cluster](#bootstrapping-the-cluster)
|
||||
- [etcd](#etcd)
|
||||
- [Apiserver, Controller Manager, and Scheduler](#apiserver-controller-manager-and-scheduler)
|
||||
- [Apiserver pod template](#apiserver-pod-template)
|
||||
- [Cloud Providers](#cloud-providers)
|
||||
- [Scheduler pod template](#scheduler-pod-template)
|
||||
- [Controller Manager Template](#controller-manager-template)
|
||||
- [Starting and Verifying Apiserver, Scheduler, and Controller Manager](#starting-and-verifying-apiserver-scheduler-and-controller-manager)
|
||||
- [Logging](#logging)
|
||||
- [Monitoring](#monitoring)
|
||||
- [DNS](#dns)
|
||||
- [Troubleshooting](#troubleshooting)
|
||||
- [Running validate-cluster](#running-validate-cluster)
|
||||
- [Inspect pods and services](#inspect-pods-and-services)
|
||||
- [Try Examples](#try-examples)
|
||||
- [Running the Conformance Test](#running-the-conformance-test)
|
||||
- [Networking](#networking)
|
||||
- [Getting Help](#getting-help)
|
||||
|
||||
<!-- END MUNGE: GENERATED_TOC -->
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Designing and Preparing
|
||||
|
||||
@@ -867,17 +820,4 @@ pinging or SSH-ing from one node to another.
|
||||
### Getting Help
|
||||
|
||||
If you run into trouble, please see the section on [troubleshooting](gce.html#troubleshooting), post to the
|
||||
[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](../troubleshooting.html#slack).
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](../troubleshooting.html#slack).
|
||||
@@ -1,23 +1,7 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Kubernetes Deployment On Bare-metal Ubuntu Nodes"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Kubernetes Deployment On Bare-metal Ubuntu Nodes
|
||||
------------------------------------------------
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Starting a Cluster](#starting-a-cluster)
|
||||
- [Download binaries](#download-binaries)
|
||||
- [Configure and start the kubernetes cluster](#configure-and-start-the-kubernetes-cluster)
|
||||
- [Test it out](#test-it-out)
|
||||
- [Deploy addons](#deploy-addons)
|
||||
- [Trouble shooting](#trouble-shooting)
|
||||
- [Upgrading a Cluster](#upgrading-a-cluster)
|
||||
|
||||
## Introduction
|
||||
|
||||
@@ -28,6 +12,10 @@ work, which has been merge into this document.
|
||||
|
||||
[Cloud team from Zhejiang University](https://github.com/ZJU-SEL) will maintain this work.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
1. The nodes have installed docker version 1.2+ and bridge-utils to manipulate linux bridge.
|
||||
@@ -295,16 +283,4 @@ Some examples are as follows:
|
||||
|
||||
The script will not delete any resources of your cluster, it just replaces the binaries.
|
||||
You can use `kubectl` command to check if the newly upgraded k8s is working correctly.
|
||||
For example, use `$ kubectl get nodes` to see if all of your nodes are ready.Or refer to [test-it-out](ubuntu.html#test-it-out)
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
For example, use `$ kubectl get nodes` to see if all of your nodes are ready.Or refer to [test-it-out](ubuntu.html#test-it-out)
|
||||
@@ -1,33 +1,13 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started with Vagrant"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
## Getting started with Vagrant
|
||||
|
||||
Running Kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/develop on your local machine (Linux, Mac OS X).
|
||||
|
||||
**Table of Contents**
|
||||
## Table of Contents
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Setup](#setup)
|
||||
- [Interacting with your Kubernetes cluster with Vagrant.](#interacting-with-your-kubernetes-cluster-with-vagrant)
|
||||
- [Authenticating with your master](#authenticating-with-your-master)
|
||||
- [Running containers](#running-containers)
|
||||
- [Troubleshooting](#troubleshooting)
|
||||
- [I keep downloading the same (large) box all the time!](#i-keep-downloading-the-same-large-box-all-the-time)
|
||||
- [I just created the cluster, but I am getting authorization errors!](#i-just-created-the-cluster-but-i-am-getting-authorization-errors)
|
||||
- [I just created the cluster, but I do not see my container running!](#i-just-created-the-cluster-but-i-do-not-see-my-container-running)
|
||||
- [I want to make changes to Kubernetes code!](#i-want-to-make-changes-to-kubernetes-code)
|
||||
- [I have brought Vagrant up but the nodes cannot validate!](#i-have-brought-vagrant-up-but-the-nodes-cannot-validate)
|
||||
- [I want to change the number of nodes!](#i-want-to-change-the-number-of-nodes)
|
||||
- [I want my VMs to have more memory!](#i-want-my-vms-to-have-more-memory)
|
||||
- [I ran vagrant suspend and nothing works!](#i-ran-vagrant-suspend-and-nothing-works)
|
||||
- [I want vagrant to sync folders via nfs!](#i-want-vagrant-to-sync-folders-via-nfs)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Prerequisites
|
||||
|
||||
@@ -416,17 +396,4 @@ You can ensure that vagrant uses nfs to sync folders with virtual machines by se
|
||||
{% raw %}
|
||||
export KUBERNETES_VAGRANT_USE_NFS=true
|
||||
{% endraw %}
|
||||
{% endhighlight %}
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
{% endhighlight %}
|
||||
@@ -1,25 +1,15 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Getting started with vSphere"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
Getting started with vSphere
|
||||
-------------------------------
|
||||
|
||||
The example below creates a Kubernetes cluster with 4 worker node Virtual
|
||||
Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This
|
||||
cluster is set up and controlled from your workstation (or wherever you find
|
||||
convenient).
|
||||
|
||||
**Table of Contents**
|
||||
## Table of Contents
|
||||
|
||||
- [Prerequisites](#prerequisites)
|
||||
- [Setup](#setup)
|
||||
- [Starting a cluster](#starting-a-cluster)
|
||||
- [Extra: debugging deployment failure](#extra-debugging-deployment-failure)
|
||||
{% include pagetoc.html %}
|
||||
|
||||
### Prerequisites
|
||||
|
||||
@@ -105,17 +95,4 @@ deployment works just as any other one!
|
||||
The output of `kube-up.sh` displays the IP addresses of the VMs it deploys. You
|
||||
can log into any VM as the `kube` user to poke around and figure out what is
|
||||
going on (find yourself authorized with your SSH key, or use the password
|
||||
`kube` otherwise).
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
`kube` otherwise).
|
||||
@@ -1,32 +1,15 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Kubernetes 101 - Kubectl CLI and Pods"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
# Kubernetes 101 - Kubectl CLI and Pods
|
||||
|
||||
For Kubernetes 101, we will cover kubectl, pods, volumes, and multiple containers
|
||||
|
||||
In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes).
|
||||
|
||||
**Table of Contents**
|
||||
<!-- BEGIN MUNGE: GENERATED_TOC -->
|
||||
## Table of Contents
|
||||
|
||||
- [Kubernetes 101 - Kubectl CLI and Pods](#kubernetes-101---kubectl-cli-and-pods)
|
||||
- [Kubectl CLI](#kubectl-cli)
|
||||
- [Pods](#pods)
|
||||
- [Pod Definition](#pod-definition)
|
||||
- [Pod Management](#pod-management)
|
||||
- [Volumes](#volumes)
|
||||
- [Volume Types](#volume-types)
|
||||
- [Multiple Containers](#multiple-containers)
|
||||
- [What's Next?](#whats-next)
|
||||
|
||||
<!-- END MUNGE: GENERATED_TOC -->
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Kubectl CLI
|
||||
|
||||
@@ -216,17 +199,4 @@ Finally, we have also introduced an environment variable to the `git-monitor` co
|
||||
## What's Next?
|
||||
|
||||
Continue on to [Kubernetes 201](k8s201.html) or
|
||||
for a complete application see the [guestbook example](../../../examples/guestbook/README.html)
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
for a complete application see the [guestbook example](../../../examples/guestbook/README.html)
|
||||
@@ -1,13 +1,7 @@
|
||||
---
|
||||
layout: docwithnav
|
||||
title: "Kubernetes 201 - Labels, Replication Controllers, Services and Health Checking"
|
||||
section: guides
|
||||
---
|
||||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
|
||||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||||
|
||||
# Kubernetes 201 - Labels, Replication Controllers, Services and Health Checking
|
||||
|
||||
If you went through [Kubernetes 101](README.html), you learned about kubectl, pods, volumes, and multiple containers.
|
||||
For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, deployment and
|
||||
@@ -15,22 +9,9 @@ scaling.
|
||||
|
||||
In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes).
|
||||
|
||||
**Table of Contents**
|
||||
<!-- BEGIN MUNGE: GENERATED_TOC -->
|
||||
|
||||
- [Kubernetes 201 - Labels, Replication Controllers, Services and Health Checking](#kubernetes-201---labels-replication-controllers-services-and-health-checking)
|
||||
- [Labels](#labels)
|
||||
- [Replication Controllers](#replication-controllers)
|
||||
- [Replication Controller Management](#replication-controller-management)
|
||||
- [Services](#services)
|
||||
- [Service Management](#service-management)
|
||||
- [Health Checking](#health-checking)
|
||||
- [Process Health Checking](#process-health-checking)
|
||||
- [Application Health Checking](#application-health-checking)
|
||||
- [What's Next?](#whats-next)
|
||||
|
||||
<!-- END MUNGE: GENERATED_TOC -->
|
||||
## Table of Contents
|
||||
|
||||
{% include pagetoc.html %}
|
||||
|
||||
## Labels
|
||||
|
||||
@@ -325,17 +306,4 @@ For more information about health checking, see [Container Probes](../pod-states
|
||||
|
||||
## What's Next?
|
||||
|
||||
For a complete application see the [guestbook example](../../../examples/guestbook/).
|
||||
|
||||
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: IS_VERSIONED -->
|
||||
<!-- TAG IS_VERSIONED -->
|
||||
<!-- END MUNGE: IS_VERSIONED -->
|
||||
|
||||
|
||||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||||
[]()
|
||||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|
||||
|
||||
For a complete application see the [guestbook example](../../../examples/guestbook/).
|
||||
Reference in New Issue
Block a user