mirror of https://github.com/kubernetes/kops.git
08b263b8f6
Previously k8s 1.17+ would always match with COS rather than Ubuntu 20.04 because of the unbound version range. This updates 1.18+ clusters to use Ubuntu 20.04 to match AWS. This should fix the failure to download logs via SSH here: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-gce-kubetest2/1373013584195358720 The instance groups confirm the use of COS rather than u2004: https://storage.googleapis.com/kubernetes-jenkins/logs/e2e-kops-gce-kubetest2/1373013584195358720/artifacts/instancegroups.yaml |
||
|---|---|---|
| .. | ||
| advanced | ||
| advisories | ||
| architecture | ||
| asciicast | ||
| cli | ||
| contributing | ||
| examples | ||
| getting_started | ||
| img | ||
| kops-server | ||
| networking | ||
| operations | ||
| overrides | ||
| releases | ||
| tutorial | ||
| welcome | ||
| work_in_progress | ||
| .pages | ||
| OWNERS | ||
| README.md | ||
| addons.md | ||
| authentication.md | ||
| aws-china.md | ||
| bastion.md | ||
| boot-sequence.md | ||
| changing_configuration.md | ||
| cluster_spec.md | ||
| continuous_integration.md | ||
| creating_subdomain.md | ||
| custom_ca.md | ||
| etcd3-migration.md | ||
| extra.css | ||
| gossip.md | ||
| gpu.md | ||
| horizontal_pod_autoscaling.md | ||
| http_proxy.md | ||
| iam_roles.md | ||
| index.md | ||
| install.md | ||
| instance_groups.md | ||
| labels.md | ||
| manifests_and_customizing_via_api.md | ||
| mfa.md | ||
| networking.md | ||
| node_authorization.md | ||
| node_resource_handling.md | ||
| philosophy.md | ||
| release-process.md | ||
| rotate-secrets.md | ||
| run_in_existing_vpc.md | ||
| secrets.md | ||
| security.md | ||
| security_groups.md | ||
| single-to-multi-master.md | ||
| state.md | ||
| terraform.md | ||
| topology.md | ||
| upgrade_from_k8s_12.md | ||
| upgrade_from_kubeup.md | ||
README.md
Documentation Index
For a better viewing experience please check out our live documentation site at kops.sigs.k8s.io.
Quick start
Overview
Command-line interface
- CLI argument explanations
- CLI reference
- Commands
- miscellaneous CLI-related remarks
- Experimental features
- list of and how to enable experimental flags in the CLI
- kubectl
- how to point kubectl to your
kopscluster
- how to point kubectl to your
Advanced / Detailed List of Configurations
API / Configuration References
API Usage Guides
kopscluster API definitions- overview of some of the API value to customize a
kopscluster
- overview of some of the API value to customize a
kopsinstance groups API- overview of some of the API value to customize a
kopsgroups of k8s nodes
- overview of some of the API value to customize a
- Using Manifests and Customizing via the API
Operations
- Cluster addon manager
- Cluster addons
- Cluster configuration management
- Cluster desired configuration creation from template
- Cluster upgrades and migrations
etcdvolume encryption setupetcdbackup/restore- GPU setup
- High Availability
- InstanceGroup Images
- how to use other image for cluster nodes, and information on available/tested images
k8supgradingkopsupdatingkube-uptokopsupgrade- Label management
- for cluster nodes
- Secret management
- Service Account Token Volume Projection
- Moving from a Single Master to Multiple HA Masters
- Upgrading Kubernetes
- Working with Instance Groups
- Running
kopsin a CI environment
Networking
- Networking Overview including CNI
- Run
kopsin an existing VPC - Supported network topologies
- Subdomain setup
kops design documents
Security
- Bastion setup
- IAM roles
- MFA setup
- how to set up MFA for
kops
- how to set up MFA for
- Security
- overview of secret storage, SSH credentials etc.
Inspection
- Download
kopsconfiguration- methods to download the current generated
kopsconfiguration
- methods to download the current generated
- Get AWS subdomain NS records
Development
- Developing using Docker
- Documentation Guidelines
- E2E testing with
kopsclusters - Example on how to add a feature
- Hack Directory
- How to update
kopsAPI - Low level description on how kops works
- Notes on Gossip design
- Notes on master instance sizing
- Our release process
- Releasing with Homebrew
- Rolling Update Diagrams