mirror of https://github.com/kubernetes/kops.git
As etcd is running directly as a service on the master nodes it is easy to overlook that different ports are needed to expose metrics for multiple etcd clusters on the master nodes. It can be easy to forget this if you otherwise just deal with containers and pods... 😅 A reminder and clarification doesn't hurt.
|
||
---|---|---|
.. | ||
advanced | ||
advisories | ||
architecture | ||
asciicast | ||
cli | ||
contributing | ||
examples | ||
getting_started | ||
img | ||
kops-server | ||
networking | ||
operations | ||
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 | ||
run_in_existing_vpc.md | ||
secrets.md | ||
security.md | ||
security_groups.md | ||
single-to-multi-master.md | ||
state.md | ||
terraform.md | ||
topology.md | ||
values.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
kops
cluster
- how to point kubectl to your
Advanced / Detailed List of Configurations
API / Configuration References
API Usage Guides
kops
cluster API definitions- overview of some of the API value to customize a
kops
cluster
- overview of some of the API value to customize a
kops
instance groups API- overview of some of the API value to customize a
kops
groups 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
etcd
volume encryption setupetcd
backup/restore- GPU setup
- High Availability
- InstanceGroup Images
- how to use other image for cluster nodes, and information on available/tested images
k8s
upgradingkops
updating- 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
kops
in a CI environment
Networking
- Networking Overview including CNI
- Run
kops
in 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
kops
configuration- methods to download the current generated
kops
configuration
- methods to download the current generated
- Get AWS subdomain NS records
Development
- Developing using Docker
- Documentation Guidelines
- E2E testing with
kops
clusters - Example on how to add a feature
- Hack Directory
- How to update
kops
API - 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