Add tables of contents to getting started guides.
This commit is contained in:
@@ -1,5 +1,17 @@
|
||||
# Kubernetes on Azure with CoreOS and [Weave](http://weave.works)
|
||||
|
||||
## Contents
|
||||
|
||||
- [Kubernetes on Azure with CoreOS and [Weave](http://weave.works)](#kubernetes-on-azure-with-coreos-and-weavehttpweaveworks)
|
||||
- [Contents](#contents)
|
||||
- [Introduction](#introduction)
|
||||
- [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.
|
||||
|
@@ -1,6 +1,27 @@
|
||||
# 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.
|
||||
|
||||
## Contents
|
||||
|
||||
- [Bare Metal CoreOS with Kubernetes (OFFLINE)](#bare-metal-coreos-with-kubernetes-offline)
|
||||
- [Contents](#contents)
|
||||
- [High Level Design](#high-level-design)
|
||||
- [Pre-requisites](#pre-requisites)
|
||||
- [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)
|
||||
- [cloud-config](#cloud-config)
|
||||
- [node.yml](#nodeyml)
|
||||
- [cloud-config](#cloud-config)
|
||||
- [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)
|
||||
|
||||
|
||||
## High Level Design
|
||||
1. Manage the tftp directory
|
||||
@@ -159,7 +180,7 @@ This section covers configuring the DHCP server to hand out our new images. In t
|
||||
|
||||
We will be specifying the node configuration later in the guide.
|
||||
|
||||
# Kubernetes
|
||||
## Kubernetes
|
||||
To deploy our configuration we need to create an ```etcd``` master. To do so we want to pxe CoreOS with a specific cloud-config.yml. There are two options we have here.
|
||||
1. Is to template the cloud config file and programmatically create new static configs for different cluster setups.
|
||||
2. Have a service discovery protocol running in our stack to do auto discovery.
|
||||
|
Reference in New Issue
Block a user