mirror of https://github.com/kubernetes/kops.git
576dca6fb7
Automatic merge from submit-queue AWS: root volume provisioned IOPS support It is possible to set `rootVolumeType: gp2` so an instance group will use `gp2` as disk type (https://github.com/kubernetes/kops/blob/master/docs/instance_groups.md) If the option is set to `rootVolumeType: io1` then the below error is thrown when building the cluster: `W0731 13:44:44.298875 8784 executor.go:109] error running task "LaunchConfiguration/master-eu-west-1a.masters.cluster.name" (9m48s remaining to succeed): error creating AutoscalingLaunchConfiguration: ValidationError: Iops is required for a provisioned IOPS volume. status code: 400, request id: 072e23b2-75ee-11e7-968a-191d6f6e9343` This PR tries to address this so if anyone needs, it can use `io1` as disk type for the root volume. In order to define the number of Iops set `rootVolumeIops: <number>` (minimum is 100) If `rootVolumeType: io1` is set and `rootVolumeIops` is not defined, then `rootVolumeIops` defaults to 100. I am not quite familiar with the Kops codebase and this is my first encounter with Go, so some changes might not be suitable (I also do not have a software developer background so bear with me :) ). Please review and add feed-back. I've included a small change to the Makefile as I compiled Kops on a Mac and didn't had $GOPATH set after installing Go. I thought that pulling this via `go env` would be more flexible, but I am not 100% sure as I don't do much development in this area and not sure about possible use cases. |
||
|---|---|---|
| .. | ||
| api-server | ||
| apireference | ||
| asciicast | ||
| calico_cidr_migration | ||
| cli | ||
| development | ||
| img | ||
| releases | ||
| work_in_progress | ||
| README.md | ||
| addon_manager.md | ||
| addons.md | ||
| arguments.md | ||
| aws.md | ||
| bastion.md | ||
| boot-sequence.md | ||
| changing_configuration.md | ||
| cluster_spec.md | ||
| cluster_upgrades_and_migrations.md | ||
| commands.md | ||
| creating_subdomain.md | ||
| download_config.md | ||
| etcd_backup.md | ||
| etcd_volume_encryption.md | ||
| experimental.md | ||
| gpu.md | ||
| high_availability.md | ||
| iam_roles.md | ||
| images.md | ||
| install.md | ||
| instance_groups.md | ||
| kubectl.md | ||
| labels.md | ||
| manifests_and_customizing_via_api.md | ||
| mfa.md | ||
| networking.md | ||
| ns.md | ||
| philosophy.md | ||
| releases.md | ||
| run_in_existing_vpc.md | ||
| secrets.md | ||
| security.md | ||
| single-to-multi-master.md | ||
| state.md | ||
| terraform.md | ||
| topology.md | ||
| update_kops.md | ||
| upgrade.md | ||
| upgrade_from_k8s_12.md | ||
| upgrade_from_kops_1.6_to_1.7_calico_cidr_migration.md | ||
| upgrade_from_kubeup.md | ||
| vsphere-dev.md | ||
| vsphere-development-status.md | ||
README.md
Documentation Index
Quick start
Overview
- Getting started on AWS
- Command-line interface
- Inspection
kopsdesign documents- Networking
- Operations
- Security
- Workflows
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 upgrades and migrations
etcdvolume encryption setupetcdbackup setup- 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
- Moving from a Single Master to Multiple HA Masters
- Developers guide for vSphere support
- vSphere support status
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
- Development with vSphere
- 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
- Updating Go Dependencies