diff --git a/content/en/docs/admin/high-availability/OWNERS b/content/en/docs/admin/high-availability/OWNERS deleted file mode 100644 index 5c5ac0bdc24f9..0000000000000 --- a/content/en/docs/admin/high-availability/OWNERS +++ /dev/null @@ -1,4 +0,0 @@ -reviewers: -- davidopp -- lavalamp - diff --git a/content/en/docs/admin/high-availability/building.md b/content/en/docs/admin/high-availability/building.md deleted file mode 100644 index fcbab6ccf0bf4..0000000000000 --- a/content/en/docs/admin/high-availability/building.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -title: Building High-Availability Clusters ---- - -## Introduction - -This document describes how to build a high-availability (HA) Kubernetes cluster. This is a fairly advanced topic. -Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such -as [Minikube](/docs/getting-started-guides/minikube/) -or try [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) for hosted Kubernetes. - -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. - -* TOC -{{< toc >}} - -## Overview - -Setting up a truly reliable, highly available distributed system requires a number of steps. It is akin to -wearing underwear, pants, a belt, suspenders, another pair of underwear, and another pair of pants. We go into each -of these steps in detail, but a summary is given here to help guide and orient the user. - -The steps involved are as follows: - - * [Creating the reliable constituent nodes that collectively form our HA master implementation.](#reliable-nodes) - * [Setting up a redundant, reliable storage layer with clustered etcd.](#establishing-a-redundant-reliable-data-storage-layer) - * [Starting replicated, load balanced Kubernetes API servers](#replicated-api-servers) - * [Setting up master-elected Kubernetes scheduler and controller-manager daemons](#master-elected-components) - -Here's what the system should look like when it's finished: - -![High availability Kubernetes diagram](/images/docs/ha.svg) - -## Initial set-up - -The remainder of this guide assumes that you are setting up a 3-node clustered master, where each machine is running some flavor of Linux. -Examples in the guide are given for Debian distributions, but they should be easily adaptable to other distributions. -Likewise, this set up should work whether you are running in a public or private cloud provider, or if you are running -on bare metal. - -The easiest way to implement an HA Kubernetes cluster is to start with an existing single-master cluster. The -instructions at [https://get.k8s.io](https://get.k8s.io) -describe easy installation for single-master clusters on a variety of platforms. - -## Reliable nodes - -On each master node, we are going to run a number of processes that implement the Kubernetes API. The first step in making these reliable is -to make sure that each automatically restarts when it fails. To achieve this, we need to install a process watcher. We choose to use -the `kubelet` that we run on each of the worker nodes. This is convenient, since we can use containers to distribute our binaries, we can -establish resource limits, and introspect the resource usage of each daemon. Of course, we also need something to monitor the kubelet -itself (insert who watches the watcher jokes here). For Debian systems, we choose monit, but there are a number of alternate -choices. For example, on systemd-based systems (e.g. RHEL, CentOS), you can run 'systemctl enable kubelet'. - -If you are extending from a standard Kubernetes installation, the `kubelet` binary should already be present on your system. You can run -`which kubelet` to determine if the binary is in fact installed. If it is not installed, -you should install the [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet) and [default-kubelet](/docs/admin/high-availability/default-kubelet) -scripts. - -If you are using monit, you should also install the monit daemon (`apt-get install monit`) and the [monit-kubelet](/docs/admin/high-availability/monit-kubelet) and -[monit-docker](/docs/admin/high-availability/monit-docker) configs. - -On systemd systems you `systemctl enable kubelet` and `systemctl enable docker`. - -## Establishing a redundant, reliable data storage layer - -The central foundation of a highly available solution is a redundant, reliable storage layer. The number one rule of high-availability is -to protect the data. Whatever else happens, whatever catches on fire, if you have the data, you can rebuild. If you lose the data, you're -done. - -Clustered etcd already replicates your storage to all master instances in your cluster. This means that to lose data, all three nodes would need -to have their physical (or virtual) disks fail at the same time. The probability that this occurs is relatively low, so for many people -running a replicated etcd cluster is likely reliable enough. You can add additional reliability by increasing the -size of the cluster from three to five nodes. If that is still insufficient, you can add -[even more redundancy to your storage layer](#even-more-reliable-storage). - -### Clustering etcd - -The full details of clustering etcd are beyond the scope of this document, lots of details are given on the -[etcd clustering page](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/clustering.md). This example walks through -a simple cluster set up, using etcd's built in discovery to build our cluster. - -First, hit the etcd discovery service to create a new token: - -```shell -curl https://discovery.etcd.io/new?size=3 -``` - -On each node, copy the [etcd.yaml](/docs/admin/high-availability/etcd.yaml) file into `/etc/kubernetes/manifests/etcd.yaml` - -The kubelet on each node actively monitors the contents of that directory, and it will create an instance of the `etcd` -server from the definition of the pod specified in `etcd.yaml`. - -Note that in `etcd.yaml` you should substitute the token URL you got above for `${DISCOVERY_TOKEN}` on all three machines, -and you should substitute a different name (e.g. `node-1`) for `${NODE_NAME}` and the correct IP address -for `${NODE_IP}` on each machine. - -#### Validating your cluster - -Once you copy this into all three nodes, you should have a clustered etcd set up. You can validate on master with - -```shell -kubectl exec etcdctl member list -``` - -and - -```shell -kubectl exec etcdctl cluster-health -``` - -You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcdctl get foo` -on a different node. - -### Even more reliable storage - -Of course, if you are interested in increased data reliability, there are further options which make the place where etcd -installs its data even more reliable than regular disks (belts *and* suspenders, ftw!). - -If you use a cloud provider, then they usually provide this -for you, for example [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) on the Google Cloud Platform. These -are block-device persistent storage that can be mounted onto your virtual machine. Other cloud providers provide similar solutions. - -If you are running on physical machines, you can also use network attached redundant storage using an iSCSI or NFS interface. -Alternatively, you can run a clustered file system like Gluster or Ceph. Finally, you can also run a RAID array on each physical machine. - -Regardless of how you choose to implement it, if you chose to use one of these options, you should make sure that your storage is mounted -to each machine. If your storage is shared between the three masters in your cluster, you should create a different directory on the storage -for each node. Throughout these instructions, we assume that this storage is mounted to your machine in `/var/etcd/data`. - -## Replicated API Servers - -Once you have replicated etcd set up correctly, we will also install the apiserver using the kubelet. - -### Installing configuration files - -First you need to create the initial log file, so that Docker mounts a file instead of a directory: - -```shell -touch /var/log/kube-apiserver.log -``` - -Next, you need to create a `/srv/kubernetes/` directory on each node. This directory includes: - - * basic_auth.csv - basic auth user and password - * ca.crt - Certificate Authority cert - * known_tokens.csv - tokens that entities (e.g. the kubelet) can use to talk to the apiserver - * kubecfg.crt - Client certificate, public key - * kubecfg.key - Client certificate, private key - * server.cert - Server certificate, public key - * server.key - Server certificate, private key - -The easiest way to create this directory, may be to copy it from the master node of a working cluster, or you can manually generate these files yourself. - -### Starting the API Server - -Once these files exist, copy the [kube-apiserver.yaml](/docs/admin/high-availability/kube-apiserver.yaml) into `/etc/kubernetes/manifests/` on each master node. - -The kubelet monitors this directory, and will automatically create an instance of the `kube-apiserver` container using the pod definition specified -in the file. - -### Load balancing - -At this point, you should have 3 apiservers all working correctly. If you set up a network load balancer, you should -be able to access your cluster via that load balancer, and see traffic balancing between the apiserver instances. Setting -up a load balancer will depend on the specifics of your platform, for example instructions for the Google Cloud -Platform can be found [here](https://cloud.google.com/compute/docs/load-balancing/). - -Note, if you are using authentication, you may need to regenerate your certificate to include the IP address of the balancer, -in addition to the IP addresses of the individual nodes. - -For pods that you deploy into the cluster, the `kubernetes` service/dns name should provide a load balanced endpoint for the master automatically. - -For external users of the API (e.g. the `kubectl` command line interface, continuous build pipelines, or other clients) you will want to configure -them to talk to the external load balancer's IP address. - -### Endpoint reconciler - -As mentioned in the previous section, the apiserver is exposed through a -service called `kubernetes`. The endpoints for this service correspond to -the apiserver replicas that we just deployed. - -Since updating endpoints and services requires the apiserver to be up, there -is special code in the apiserver to let it update its own endpoints directly. -This code is called the "reconciler," because it reconciles the list of -endpoints stored in etcd, and the list of endpoints that are actually up -and running. - -Prior to Kubernetes 1.9, the reconciler expects you to provide the -number of endpoints (i.e., the number of apiserver replicas) through -a command-line flag (e.g. `--apiserver-count=3`). If more replicas -are available, the reconciler trims down the list of endpoints. -As a result, if a node running a replica of the apiserver crashes -and gets replaced, the list of endpoints is eventually updated. -However, until the replica gets replaced, its endpoint stays in -the list. During that time, a fraction of the API requests sent -to the `kubernetes` service will fail, because they will be sent -to a down endpoint. - -This is why the previous section advises you to deploy a load -balancer, and access the API through that load balancer. The -load balancer will directly assess the health of the apiserver -replicas, and make sure that requests are not sent to crashed -instances. - -If you do not add the `--apiserver-count` flag, the value defaults to 1. -Your cluster will work correctly, but each apiserver replica will -continuously try to add itself to the list of endpoints while removing -the other ones, causing a lot of extraneous updates in kube-proxy -and other components. - -Starting with Kubernetes 1.9, a new alpha reconciler implementation is -available. It uses a *lease* that is regularly renewed by each apiserver -replica. When a replica is down, it stops renewing its lease, and the other -replicas notice that the lease expired and remove it from the list of -endpoints. You can switch to the new reconciler by adding the flag -`--endpoint-reconciler-type=lease` when starting your apiserver replicas. - -{{< feature-state state="alpha" >}} - -If you want to know more, you can check the following resources: - -- [issue kubernetes/kubernetes#22609](https://github.com/kubernetes/kubernetes/issues/22609), - which gives additional context -- [master/reconcilers/mastercount.go](https://github.com/kubernetes/kubernetes/blob/dd9981d038012c120525c9e6df98b3beb3ef19e1/pkg/master/reconcilers/mastercount.go#L63), - the implementation of the master count reconciler -- [PR kubernetes/kubernetes#51698](https://github.com/kubernetes/kubernetes/pull/51698), - which adds support for the lease reconciler - -## Master elected components - -So far we have set up state storage, and we have set up the API server, but we haven't run anything that actually modifies -cluster state, such as the controller manager and scheduler. To achieve this reliably, we only want to have one actor modifying state at a time, but we want replicated -instances of these actors, in case a machine dies. To achieve this, we are going to use a lease-lock in the API to perform -master election. We will use the `--leader-elect` flag for each scheduler and controller-manager, using a lease in the API will ensure that only 1 instance of the scheduler and controller-manager are running at once. - -The scheduler and controller-manager can be configured to talk to the API server that is on the same node (i.e. 127.0.0.1), or it can be configured to communicate using the load balanced IP address of the API servers. Regardless of how they are configured, the scheduler and controller-manager will complete the leader election process mentioned above when using the `--leader-elect` flag. - -In case of a failure accessing the API server, the elected leader will not be able to renew the lease, causing a new leader to be elected. This is especially relevant when configuring the scheduler and controller-manager to access the API server via 127.0.0.1, and the API server on the same node is unavailable. - -### Installing configuration files - -First, create empty log files on each node, so that Docker will mount the files not make new directories: - -```shell -touch /var/log/kube-scheduler.log -touch /var/log/kube-controller-manager.log -``` - -Next, set up the descriptions of the scheduler and controller manager pods on each node by copying [kube-scheduler.yaml](/docs/admin/high-availability/kube-scheduler.yaml) and [kube-controller-manager.yaml](/docs/admin/high-availability/kube-controller-manager.yaml) into the `/etc/kubernetes/manifests/` directory. - -## Conclusion - -At this point, you are done (yeah!) with the master components, but you still need to add worker nodes (boo!). - -If you have an existing cluster, this is as simple as reconfiguring your kubelets to talk to the load-balanced endpoint, and -restarting the kubelets on each node. - -If you are turning up a fresh cluster, you will need to install the kubelet and kube-proxy on each worker node, and -set the `--apiserver` flag to your replicated endpoint. diff --git a/content/en/docs/admin/high-availability/default-kubelet b/content/en/docs/admin/high-availability/default-kubelet deleted file mode 100644 index 2ff0eb80ccbbc..0000000000000 --- a/content/en/docs/admin/high-availability/default-kubelet +++ /dev/null @@ -1,8 +0,0 @@ -# This should be the IP address of the load balancer for all masters -MASTER_IP= -# This should be the internal service IP address reserved for DNS -DNS_IP= - -DAEMON_ARGS="$DAEMON_ARGS --api-servers=https://${MASTER_IP} --enable-debugging-handlers=true --cloud-provider= -gce --pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=False --v=2 --cluster-dns=${DNS_IP} --cluster-domain=c -luster.local --configure-cbr0=true --cgroup-root=/ --system-container=/system " diff --git a/content/en/docs/admin/high-availability/etcd.yaml b/content/en/docs/admin/high-availability/etcd.yaml deleted file mode 100644 index 364791da6fe26..0000000000000 --- a/content/en/docs/admin/high-availability/etcd.yaml +++ /dev/null @@ -1,87 +0,0 @@ -apiVersion: v1 -kind: Pod -metadata: - name: etcd-server -spec: - hostNetwork: true - containers: - - image: k8s.gcr.io/etcd:3.0.17 - name: etcd-container - command: - - /usr/local/bin/etcd - - --name - - ${NODE_NAME} - - --initial-advertise-peer-urls - - http://${NODE_IP}:2380 - - --listen-peer-urls - - http://${NODE_IP}:2380 - - --advertise-client-urls - - http://${NODE_IP}:4001 - - --listen-client-urls - - http://127.0.0.1:4001 - - --data-dir - - /var/etcd/data - - --discovery - - ${DISCOVERY_TOKEN} - ports: - - containerPort: 2380 - hostPort: 2380 - name: serverport - - containerPort: 4001 - hostPort: 4001 - name: clientport - volumeMounts: - - mountPath: /var/etcd - name: varetcd - - mountPath: /etc/ssl - name: etcssl - readOnly: true - - mountPath: /usr/share/ssl - name: usrsharessl - readOnly: true - - mountPath: /var/ssl - name: varssl - readOnly: true - - mountPath: /usr/ssl - name: usrssl - readOnly: true - - mountPath: /usr/lib/ssl - name: usrlibssl - readOnly: true - - mountPath: /usr/local/openssl - name: usrlocalopenssl - readOnly: true - - mountPath: /etc/openssl - name: etcopenssl - readOnly: true - - mountPath: /etc/pki/tls - name: etcpkitls - readOnly: true - volumes: - - hostPath: - path: /var/etcd/data - name: varetcd - - hostPath: - path: /etc/ssl - name: etcssl - - hostPath: - path: /usr/share/ssl - name: usrsharessl - - hostPath: - path: /var/ssl - name: varssl - - hostPath: - path: /usr/ssl - name: usrssl - - hostPath: - path: /usr/lib/ssl - name: usrlibssl - - hostPath: - path: /usr/local/openssl - name: usrlocalopenssl - - hostPath: - path: /etc/openssl - name: etcopenssl - - hostPath: - path: /etc/pki/tls - name: etcpkitls diff --git a/content/en/docs/admin/high-availability/kube-apiserver.yaml b/content/en/docs/admin/high-availability/kube-apiserver.yaml deleted file mode 100644 index af5b1812e8b45..0000000000000 --- a/content/en/docs/admin/high-availability/kube-apiserver.yaml +++ /dev/null @@ -1,90 +0,0 @@ -apiVersion: v1 -kind: Pod -metadata: - name: kube-apiserver -spec: - hostNetwork: true - containers: - - name: kube-apiserver - image: k8s.gcr.io/kube-apiserver:9680e782e08a1a1c94c656190011bd02 - command: - - /bin/sh - - -c - - /usr/local/bin/kube-apiserver --address=127.0.0.1 --etcd-servers=http://127.0.0.1:4001 - --cloud-provider=gce --enable-admission-plugins=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota - --service-cluster-ip-range=10.0.0.0/16 --client-ca-file=/srv/kubernetes/ca.crt - --basic-auth-file=/srv/kubernetes/basic_auth.csv --cluster-name=e2e-test-bburns - --tls-cert-file=/srv/kubernetes/server.cert --tls-private-key-file=/srv/kubernetes/server.key - --secure-port=443 --token-auth-file=/srv/kubernetes/known_tokens.csv --v=2 - --allow-privileged=False 1>>/var/log/kube-apiserver.log 2>&1 - ports: - - containerPort: 443 - hostPort: 443 - name: https - - containerPort: 7080 - hostPort: 7080 - name: http - - containerPort: 8080 - hostPort: 8080 - name: local - volumeMounts: - - mountPath: /srv/kubernetes - name: srvkube - readOnly: true - - mountPath: /var/log/kube-apiserver.log - name: logfile - - mountPath: /etc/ssl - name: etcssl - readOnly: true - - mountPath: /usr/share/ssl - name: usrsharessl - readOnly: true - - mountPath: /var/ssl - name: varssl - readOnly: true - - mountPath: /usr/ssl - name: usrssl - readOnly: true - - mountPath: /usr/lib/ssl - name: usrlibssl - readOnly: true - - mountPath: /usr/local/openssl - name: usrlocalopenssl - readOnly: true - - mountPath: /etc/openssl - name: etcopenssl - readOnly: true - - mountPath: /etc/pki/tls - name: etcpkitls - readOnly: true - volumes: - - hostPath: - path: /srv/kubernetes - name: srvkube - - hostPath: - path: /var/log/kube-apiserver.log - name: logfile - - hostPath: - path: /etc/ssl - name: etcssl - - hostPath: - path: /usr/share/ssl - name: usrsharessl - - hostPath: - path: /var/ssl - name: varssl - - hostPath: - path: /usr/ssl - name: usrssl - - hostPath: - path: /usr/lib/ssl - name: usrlibssl - - hostPath: - path: /usr/local/openssl - name: usrlocalopenssl - - hostPath: - path: /etc/openssl - name: etcopenssl - - hostPath: - path: /etc/pki/tls - name: etcpkitls diff --git a/content/en/docs/admin/high-availability/kube-controller-manager.yaml b/content/en/docs/admin/high-availability/kube-controller-manager.yaml deleted file mode 100644 index ba481fbfc3956..0000000000000 --- a/content/en/docs/admin/high-availability/kube-controller-manager.yaml +++ /dev/null @@ -1,82 +0,0 @@ -apiVersion: v1 -kind: Pod -metadata: - name: kube-controller-manager -spec: - containers: - - command: - - /bin/sh - - -c - - /usr/local/bin/kube-controller-manager --master=127.0.0.1:8080 --cluster-name=e2e-test-bburns - --cluster-cidr=10.245.0.0/16 --allocate-node-cidrs=true --cloud-provider=gce --service-account-private-key-file=/srv/kubernetes/server.key - --v=2 --leader-elect=true 1>>/var/log/kube-controller-manager.log 2>&1 - image: k8s.gcr.io/kube-controller-manager:fda24638d51a48baa13c35337fcd4793 - livenessProbe: - httpGet: - path: /healthz - port: 10252 - initialDelaySeconds: 15 - timeoutSeconds: 1 - name: kube-controller-manager - volumeMounts: - - mountPath: /srv/kubernetes - name: srvkube - readOnly: true - - mountPath: /var/log/kube-controller-manager.log - name: logfile - - mountPath: /etc/ssl - name: etcssl - readOnly: true - - mountPath: /usr/share/ssl - name: usrsharessl - readOnly: true - - mountPath: /var/ssl - name: varssl - readOnly: true - - mountPath: /usr/ssl - name: usrssl - readOnly: true - - mountPath: /usr/lib/ssl - name: usrlibssl - readOnly: true - - mountPath: /usr/local/openssl - name: usrlocalopenssl - readOnly: true - - mountPath: /etc/openssl - name: etcopenssl - readOnly: true - - mountPath: /etc/pki/tls - name: etcpkitls - readOnly: true - hostNetwork: true - volumes: - - hostPath: - path: /srv/kubernetes - name: srvkube - - hostPath: - path: /var/log/kube-controller-manager.log - name: logfile - - hostPath: - path: /etc/ssl - name: etcssl - - hostPath: - path: /usr/share/ssl - name: usrsharessl - - hostPath: - path: /var/ssl - name: varssl - - hostPath: - path: /usr/ssl - name: usrssl - - hostPath: - path: /usr/lib/ssl - name: usrlibssl - - hostPath: - path: /usr/local/openssl - name: usrlocalopenssl - - hostPath: - path: /etc/openssl - name: etcopenssl - - hostPath: - path: /etc/pki/tls - name: etcpkitls diff --git a/content/en/docs/admin/high-availability/kube-scheduler.yaml b/content/en/docs/admin/high-availability/kube-scheduler.yaml deleted file mode 100644 index b4ef0e466e8cb..0000000000000 --- a/content/en/docs/admin/high-availability/kube-scheduler.yaml +++ /dev/null @@ -1,27 +0,0 @@ -apiVersion: v1 -kind: Pod -metadata: - name: kube-scheduler -spec: - hostNetwork: true - containers: - - name: kube-scheduler - image: k8s.gcr.io/kube-scheduler:34d0b8f8b31e27937327961528739bc9 - command: - - /bin/sh - - -c - - /usr/local/bin/kube-scheduler --master=127.0.0.1:8080 --v=2 --leader-elect=true 1>>/var/log/kube-scheduler.log - 2>&1 - livenessProbe: - httpGet: - path: /healthz - port: 10251 - initialDelaySeconds: 15 - timeoutSeconds: 1 - volumeMounts: - - mountPath: /var/log/kube-scheduler.log - name: logfile - volumes: - - hostPath: - path: /var/log/kube-scheduler.log - name: logfile diff --git a/content/en/docs/admin/high-availability/monit-docker b/content/en/docs/admin/high-availability/monit-docker deleted file mode 100644 index 8c2753a430a58..0000000000000 --- a/content/en/docs/admin/high-availability/monit-docker +++ /dev/null @@ -1,9 +0,0 @@ -check process docker with pidfile /var/run/docker.pid -group docker -start program = "/etc/init.d/docker start" -stop program = "/etc/init.d/docker stop" -if does not exist then restart -if failed - unixsocket /var/run/docker.sock - protocol HTTP request "/version" -then restart \ No newline at end of file diff --git a/content/en/docs/admin/high-availability/monit-kubelet b/content/en/docs/admin/high-availability/monit-kubelet deleted file mode 100644 index eb3211b06a389..0000000000000 --- a/content/en/docs/admin/high-availability/monit-kubelet +++ /dev/null @@ -1,11 +0,0 @@ -check process kubelet with pidfile /var/run/kubelet.pid -group kubelet -start program = "/etc/init.d/kubelet start" -stop program = "/etc/init.d/kubelet stop" -if does not exist then restart -if failed - host 127.0.0.1 - port 10255 - protocol HTTP - request "/healthz" -then restart diff --git a/content/en/docs/admin/high-availability/podmaster.yaml b/content/en/docs/admin/high-availability/podmaster.yaml deleted file mode 100644 index cd20e15b38f38..0000000000000 --- a/content/en/docs/admin/high-availability/podmaster.yaml +++ /dev/null @@ -1,43 +0,0 @@ -apiVersion: v1 -kind: Pod -metadata: - name: scheduler-master -spec: - hostNetwork: true - containers: - - name: scheduler-elector - image: k8s.gcr.io/podmaster:1.1 - command: - - /podmaster - - --etcd-servers=http://127.0.0.1:4001 - - --key=scheduler - - --source-file=/kubernetes/kube-scheduler.manifest - - --dest-file=/manifests/kube-scheduler.manifest - volumeMounts: - - mountPath: /kubernetes - name: k8s - readOnly: true - - mountPath: /manifests - name: manifests - - name: controller-manager-elector - image: k8s.gcr.io/podmaster:1.1 - command: - - /podmaster - - --etcd-servers=http://127.0.0.1:4001 - - --key=controller - - --source-file=/kubernetes/kube-controller-manager.manifest - - --dest-file=/manifests/kube-controller-manager.manifest - terminationMessagePath: /dev/termination-log - volumeMounts: - - mountPath: /kubernetes - name: k8s - readOnly: true - - mountPath: /manifests - name: manifests - volumes: - - hostPath: - path: /srv/kubernetes - name: k8s - - hostPath: - path: /etc/kubernetes/manifests - name: manifests diff --git a/static/_redirects b/static/_redirects index 5a34de699897a..304d17d12e27f 100644 --- a/static/_redirects +++ b/static/_redirects @@ -508,3 +508,5 @@ https://kubernetes-io-v1-7.netlify.com/* https://v1-7.docs.kubernetes.io/:spl /docs/admin/authorization/rbac/ /docs/reference/access-authn-authz/rbac/ 301 /docs/admin/authorization/webhook/ /docs/reference/access-authn-authz/webhook/ 301 /docs/admin/authorization/ /docs/reference/access-authn-authz/authorization/ 301 + +/docs/admin/high-availability/building/ /docs/setup/independent/high-availability/ 301 diff --git a/test/examples_test.go b/test/examples_test.go index 29671c00fdc47..114cb7f866527 100644 --- a/test/examples_test.go +++ b/test/examples_test.go @@ -267,13 +267,6 @@ func walkConfigFiles(inDir string, fn func(name, path string, data [][]byte)) er func TestExampleObjectSchemas(t *testing.T) { // Please help maintain the alphabeta order in the map cases := map[string]map[string][]runtime.Object{ - "docs/admin/high-availability": { - "etcd": {&api.Pod{}}, - "kube-apiserver": {&api.Pod{}}, - "kube-controller-manager": {&api.Pod{}}, - "kube-scheduler": {&api.Pod{}}, - "podmaster": {&api.Pod{}}, - }, "docs/admin/limitrange": { "invalid-pod": {&api.Pod{}}, "limits": {&api.LimitRange{}},