whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Administering Cluters section; Edit This Page funcitonality

Browse Source
This commit is contained in:
John Mulhausen
2016-02-11 02:15:49 -08:00
parent 5a960ec8e7
commit f782b2e0fb
439 changed files with 156 additions and 86841 deletions
Download Patch File Download Diff File Expand all files Collapse all files
v1.1/docs/admin/cluster-large.md
+7 -22
View File
@@ -1,18 +1,16 @@
---
layout: docwithnav
title: "Kubernetes Large Cluster"
title: "Using Large Clusters"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
# Kubernetes Large Cluster
## Support
At v1.0, Kubernetes supports clusters up to 100 nodes with 30 pods per node and 1-2 containers per pod.
## Table of Contents
{% include pagetoc.html %}
## Setup
A cluster is a set of nodes (physical or virtual machines) running Kubernetes agents, managed by a "master" (the cluster-level control plane).
@@ -70,17 +68,4 @@ To avoid running into cluster addon resource issues, when creating a cluster wit
* [FluentD with ElasticSearch Plugin](http://releases.k8s.io/release-1.1/cluster/saltbase/salt/fluentd-es/fluentd-es.yaml)
* [FluentD with GCP Plugin](http://releases.k8s.io/release-1.1/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml)
For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](../user-guide/compute-resources.html#troubleshooting).
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/cluster-large.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](../user-guide/compute-resources.html#troubleshooting).
v1.1/docs/admin/high-availability.md
+6 -45
View File
@@ -1,37 +1,7 @@
---
layout: docwithnav
title: "High Availability Kubernetes Clusters"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
# High Availability Kubernetes Clusters
**Table of Contents**
<!-- BEGIN MUNGE: GENERATED_TOC -->
- [High Availability Kubernetes Clusters](#high-availability-kubernetes-clusters)
- [Introduction](#introduction)
- [Overview](#overview)
- [Initial set-up](#initial-set-up)
- [Reliable nodes](#reliable-nodes)
- [Establishing a redundant, reliable data storage layer](#establishing-a-redundant-reliable-data-storage-layer)
- [Clustering etcd](#clustering-etcd)
- [Validating your cluster](#validating-your-cluster)
- [Even more reliable storage](#even-more-reliable-storage)
- [Replicated API Servers](#replicated-api-servers)
- [Installing configuration files](#installing-configuration-files)
- [Starting the API Server](#starting-the-api-server)
- [Load balancing](#load-balancing)
- [Master elected components](#master-elected-components)
- [Installing configuration files](#installing-configuration-files)
- [Running the podmaster](#running-the-podmaster)
- [Conclusion](#conclusion)
- [Vagrant up!](#vagrant-up)
<!-- END MUNGE: GENERATED_TOC -->
## Introduction
@@ -43,6 +13,10 @@ or try [Google Container Engine](https://cloud.google.com/container-engine/) for
Also, at this time high availability support for Kubernetes is not continuously tested in our end-to-end (e2e) testing. We will
be working to add this continuous testing, but for now the single-node master installations are more heavily tested.
## Table of Contents
{% include pagetoc.html %}
## Overview
Setting up a truly reliable, highly available distributed system requires a number of steps, it is akin to
@@ -264,17 +238,4 @@ set the `--apiserver` flag to your replicated endpoint.
We indeed have an initial proof of concept tester for this, which is available [here](https://releases.k8s.io/release-1.1/examples/high-availability).
It implements the major concepts (with a few minor reductions for simplicity), of the podmaster HA implementation alongside a quick smoke test using k8petstore.
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/high-availability.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
It implements the major concepts (with a few minor reductions for simplicity), of the podmaster HA implementation alongside a quick smoke test using k8petstore.
v1.1/docs/admin/introduction.md
+6 -21
View File
@@ -1,17 +1,15 @@
---
layout: docwithnav
title: "Kubernetes Cluster Admin Guide"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
# Kubernetes Cluster Admin Guide
The cluster admin guide is for anyone creating or administering a Kubernetes cluster.
It assumes some familiarity with concepts in the [User Guide](../user-guide/README.html).
## Table of Contents
{% include pagetoc.html %}
## Planning a cluster
There are many different examples of how to setup a kubernetes cluster. Many of them are listed in this
@@ -80,17 +78,4 @@ project](salt.html).
* **Authorization** [authorization](authorization.html)
* **Admission Controllers** [admission_controllers](admission-controllers.html)
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/introduction.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
* **Admission Controllers** [admission_controllers](admission-controllers.html)
v1.1/docs/admin/multi-cluster.md
+2 -21
View File
@@ -1,13 +1,7 @@
---
layout: docwithnav
title: "Considerations for running multiple Kubernetes clusters"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
# Considerations for running multiple Kubernetes clusters
You may want to set up multiple Kubernetes clusters, both to
have clusters in different regions to be nearer to your users, and to tolerate failures and/or invasive maintenance.
@@ -67,17 +61,4 @@ you may need even more clusters. Kubernetes v1.0 currently supports clusters up
When you have multiple clusters, you would typically create services with the same config in each cluster and put each of those
service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer) spanning all of them, so that
failures of a single cluster are not visible to end users.
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/multi-cluster.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
failures of a single cluster are not visible to end users.
v1.1/docs/admin/namespaces/README.md
+2 -21
View File
@@ -1,13 +1,7 @@
---
layout: docwithnav
title: "Kubernetes Namespaces"
section: guides
---
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
## Kubernetes Namespaces
Kubernetes _[namespaces](../../../docs/admin/namespaces.html)_ help different projects, teams, or customers to share a Kubernetes cluster.
@@ -286,17 +280,4 @@ cattle-zz7ea 1/1 Running 0 12s
At this point, it should be clear that the resources users create in one namespace are hidden from the other namespace.
As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
authorization rules for each namespace.
<!-- BEGIN MUNGE: IS_VERSIONED -->
<!-- TAG IS_VERSIONED -->
<!-- END MUNGE: IS_VERSIONED -->
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/admin/namespaces/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->
authorization rules for each namespace.