Cluster templates

This commit is contained in:
mikesplain 2019-09-14 11:18:01 -04:00
parent 1fdca28a8b
commit c818faedd2
4 changed files with 8 additions and 8 deletions

View File

@ -14,7 +14,7 @@ This strategy can be extended to sequentially upgrade Kops on multiple clusters,
This page provides examples for managing Kops clusters in CI environments.
The [Manifest documentation](./manifests_and_customizing_via_api.md) describes how to create the YAML manifest files locally and includes high level examples of commands described below.
If you have a solution for a different CI platform or deployment strategy, feel free to open a Pull Request!
If you have a solution for a different CI platform or deployment strategy, feel free to open a Pull Request!
## GitLab CI
@ -79,9 +79,9 @@ roll:
* This pipeline setup will create and update existing clusters in place. It does not perform a "blue/green" deployment of multiple clusters.
* The pipeline can be extended to support multiple clusters by making separate jobs per cluster for each stage.
Ensure the `KOPS_CLUSTER_NAME` variable is set correctly for each set of jobs.
In this case, it is possible to use `kops toolbox template` to manage one YAML template and per-cluster values files with which to render the template.
See the [Cluster Template](./cluster_template.md) documentation for more information.
See the [Cluster Template](./operations/cluster_template.md) documentation for more information.
`kops toolbox template` would then be ran before `kops replace`.
### Limitations

View File

@ -32,7 +32,7 @@ in alpha, and other platforms planned.
* Supports custom Kubernetes [add-ons](operations/addons.md)
* Command line [autocompletion](cli/kops_completion.md)
* YAML Manifest Based API [Configuration](manifests_and_customizing_via_api.md)
* [Templating](cluster_template.md) and dry-run modes for creating
* [Templating](operations/cluster_template.md) and dry-run modes for creating
Manifests
* Choose from eight different CNI [Networking](networking.md) providers out-of-the-box
* Supports upgrading from [kube-up](upgrade_from_kubeup.md)

View File

@ -1,8 +1,8 @@
# Cluster Templating
The command `kops replace` can replace a cluster desired configuration from the config in a yaml file (see [cli/kops_replace.md](cli/kops_replace.md)).
The command `kops replace` can replace a cluster desired configuration from the config in a yaml file (see [cli/kops_replace.md](../cli/kops_replace.md)).
It is possible to generate that yaml file from a template, using the command `kops toolbox template` (see [cli/kops_toolbox_template.md](cli/kops_toolbox_template.md)).
It is possible to generate that yaml file from a template, using the command `kops toolbox template` (see [cli/kops_toolbox_template.md](../cli/kops_toolbox_template.md)).
This document details the template language used.
@ -81,7 +81,7 @@ Running `kops toolbox template` replaces the placeholders in the template by val
Note: when creating a cluster desired configuration template, you can
- use `kops get k8s-cluster.example.com -o yaml > cluster-desired-config.yaml` to create the cluster desired configuration file (see [cli/kops_get.md](cli/kops_get.md)). The values in this file are defined in [cluster_spec.md](cluster_spec.md).
- use `kops get k8s-cluster.example.com -o yaml > cluster-desired-config.yaml` to create the cluster desired configuration file (see [cli/kops_get.md](../cli/kops_get.md)). The values in this file are defined in [cluster_spec.md](../cluster_spec.md).
- replace values by placeholders in that file to create the template.
### Templates

View File

@ -70,7 +70,7 @@ nav:
- Operations:
- Cluster Addons & Manager : "operations/addons.md"
- Cluster configuration management: "changing_configuration.md"
- Cluster desired configuration creation from template: "cluster_template.md"
- Cluster Templating: "operations/cluster_template.md"
- Cluster upgrades and migrations: "cluster_upgrades_and_migrations.md"
- etcd volume encryption setup: "etcd_volume_encryption.md"
- etcd backup/restore: "etcd/backup-restore.md"