mirror of https://github.com/kubernetes/kops.git
docs(addons): fix broken links
This commit is contained in:
Michael Wagner
parent
69fe8e3689
commit
ad85ca0681
|
|
@ -42,7 +42,7 @@ Para instalar un Kubernetes cluster en GCE por fabor siga esta [guide](/docs/get
|
|||
* Un Despliegue Altamente Disponible (HA) Kubernetes Masters
|
||||
* Construye en un modelo de estado sincronizado para **dry-runs** y **idempotency** automático
|
||||
* Capacidad de generar [Terraform](/docs/terraform.md)
|
||||
* Soporta un Kubernetes personalizado [add-ons](/docs/addons.md)
|
||||
* Soporta un Kubernetes personalizado [add-ons](/docs/operations/addons.md)
|
||||
* Línea de comando [autocompletion](/docs/cli/kops_completion.md)
|
||||
* YAML Archivo de Manifiesto Basado en API [Configuration](/docs/manifests_and_customizing_via_api.md)
|
||||
* [Templating](/docs/cluster_template.md) y ejecutar modos de simulacro para crear
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ To install a Kubernetes cluster on OpenStack, follow this [guide](/docs/tutorial
|
|||
* Deploys Highly Available (HA) Kubernetes Masters
|
||||
* Built on a state-sync model for **dry-runs** and automatic **idempotency**
|
||||
* Ability to generate [Terraform](/docs/terraform.md)
|
||||
* Supports custom Kubernetes [add-ons](/docs/addons.md)
|
||||
* Supports custom Kubernetes [add-ons](/docs/operations/addons.md)
|
||||
* Command line [autocompletion](/docs/cli/kops_completion.md)
|
||||
* YAML Manifest Based API [Configuration](/docs/manifests_and_customizing_via_api.md)
|
||||
* [Templating](/docs/cluster_template.md) and dry-run modes for creating
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
## Addons
|
||||
|
||||
Read on [addons](../docs/addons.md)
|
||||
Read on [addons](../docs/operations/addons.md)
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ addons:
|
|||
- manifest: ingress-citrix
|
||||
|
||||
```
|
||||
For more information on how to enable addon during cluster creation refer [Kops Addon guide](https://github.com/kubernetes/kops/blob/master/docs/addons.md#installing-kubernetes-addons)
|
||||
For more information on how to enable addon during cluster creation refer [Kops Addon guide](https://github.com/kubernetes/kops/blob/master/docs/operations/addons.md#installing-kubernetes-addons)
|
||||
|
||||
**NOTE:** This method only works for Google Cloud Platform. For using this addon on AWS, please use the `kubectl` method below.
|
||||
|
||||
|
|
|
|||
|
|
@ -357,7 +357,7 @@ func RunUpdateCluster(f *util.Factory, clusterName string, out io.Writer, c *Upd
|
|||
}
|
||||
}
|
||||
fmt.Fprintf(sb, " * the admin user is specific to Debian. If not using Debian please use the appropriate user based on your OS.\n")
|
||||
fmt.Fprintf(sb, " * read about installing addons at: https://github.com/kubernetes/kops/blob/master/docs/addons.md.\n")
|
||||
fmt.Fprintf(sb, " * read about installing addons at: https://github.com/kubernetes/kops/blob/master/docs/operations/addons.md.\n")
|
||||
fmt.Fprintf(sb, "\n")
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -48,8 +48,8 @@
|
|||
* [Using Manifests and Customizing via the API](manifests_and_customizing_via_api.md)
|
||||
|
||||
## Operations
|
||||
* [Cluster addon manager](addon_manager.md)
|
||||
* [Cluster addons](addons.md)
|
||||
* [Cluster addon manager](operations/addons.md#addon_management)
|
||||
* [Cluster addons](operations/addons.md)
|
||||
* [Cluster configuration management](changing_configuration.md)
|
||||
* [Cluster desired configuration creation from template](cluster_template.md)
|
||||
* [Cluster upgrades and migrations](operations/cluster_upgrades_and_migrations.md)
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Please follow our [basic-requirements document](basic-requirements.md) that is c
|
|||
|
||||
## DNS Setup - AWS Route53
|
||||
|
||||
For our setup we already have a hosted DNS domain in AWS:
|
||||
For our setup we already have a hosted DNS domain in AWS:
|
||||
|
||||
```bash
|
||||
aws route53 list-hosted-zones --output=table
|
||||
|
|
@ -321,7 +321,7 @@ Suggestions:
|
|||
* list nodes: kubectl get nodes --show-labels
|
||||
* ssh to the master: ssh -i ~/.ssh/id_rsa admin@api.mycluster01.kopsclustertest.example.org
|
||||
The admin user is specific to Debian. If not using Debian please use the appropriate user based on your OS.
|
||||
* read about installing addons: https://github.com/kubernetes/kops/blob/master/docs/addons.md
|
||||
* read about installing addons: https://github.com/kubernetes/kops/blob/master/docs/operations/addons.md
|
||||
```
|
||||
|
||||
Note that KOPS will create a DNS record for your API: api.mycluster01.kopsclustertest.example.org. You can check this record with the following "dig" command:
|
||||
|
|
@ -731,7 +731,7 @@ Save it and review with `kops update cluster $NAME`:
|
|||
|
||||
```bash
|
||||
kops update cluster $NAME
|
||||
```
|
||||
```
|
||||
|
||||
The last command will output:
|
||||
|
||||
|
|
@ -747,13 +747,13 @@ Will modify resources:
|
|||
MaxSize 2 -> 3
|
||||
|
||||
Must specify --yes to apply changes
|
||||
```
|
||||
```
|
||||
|
||||
Now, let's apply the change:
|
||||
|
||||
```bash
|
||||
kops update cluster $NAME --yes
|
||||
```
|
||||
```
|
||||
|
||||
Go for another coffee (or maybe a tee) and after some minutes check your cluster again with "kops validate cluster"
|
||||
|
||||
|
|
@ -784,7 +784,7 @@ Your cluster mycluster01.kopsclustertest.example.org is ready
|
|||
|
||||
```
|
||||
|
||||
You can see how your cluster scaled up to 3 nodes.
|
||||
You can see how your cluster scaled up to 3 nodes.
|
||||
|
||||
**SCALING RECOMMENDATIONS:**
|
||||
- Always think ahead. If you want to ensure to have the capability to scale-up to all available zones in the region, ensure to add them to the "--zones=" argument when using the "kops create cluster" command. Example: --zones=us-east-1a,us-east-1b,us-east-1c,us-east-1d,us-east-1e. That will make things simpler later.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
## Addons
|
||||
With kops you manage addons by using kubectl.
|
||||
|
||||
(For a description of the addon-manager, please see [addon_manager.md](#addon-management).)
|
||||
(For a description of the addon-manager, please see [addon_management](#addon-management).)
|
||||
|
||||
Addons in Kubernetes are traditionally done by copying files to `/etc/kubernetes/addons` on the master. But this
|
||||
doesn't really make sense in HA master configurations. We also have kubectl available, and addons are just a thin
|
||||
|
|
@ -21,7 +21,7 @@ This document describes how to install some common addons and how to create your
|
|||
|
||||
### Custom addons
|
||||
|
||||
The docs about the [addon manager](#addon-management) describe in more detail how to define a addon resource with regards to versioning.
|
||||
The docs about the [addon management](#addon-management) describe in more detail how to define a addon resource with regards to versioning.
|
||||
Here is a minimal example of an addon manifest that would install two different addons.
|
||||
|
||||
```yaml
|
||||
|
|
@ -155,7 +155,7 @@ The project is created by wearemolecule, and maintained at
|
|||
kubectl apply -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/route53-mapper/v1.3.0.yml
|
||||
```
|
||||
|
||||
## Addons Management
|
||||
## Addon Management
|
||||
|
||||
kops incorporates management of some addons; we _have_ to manage some addons which are needed before
|
||||
the kubernetes API is functional.
|
||||
|
|
|
|||
Loading…
Reference in New Issue