Kubernetes Cluster API Provider AWS

Kubernetes-native declarative infrastructure for AWS.

What is the Cluster API Provider AWS

The Cluster API brings declarative, Kubernetes-style APIs to cluster creation, configuration and management.

The API itself is shared across multiple cloud providers allowing for true AWS hybrid deployments of Kubernetes. It is built atop the lessons learned from previous cluster managers such as kops and kubicorn.

Documentation

Please see our book for in-depth documentation.

Launching a Kubernetes cluster on AWS

Check out the Cluster API Quick Start for launching a cluster on AWS.

Features

Native Kubernetes manifests and API
Manages the bootstrapping of VPCs, gateways, security groups and instances.
Choice of Linux distribution between Amazon Linux 2, CentOS 7 and Ubuntu 18.04, using pre-baked AMIs.
Deploys Kubernetes control planes into private subnets with a separate bastion server.
Doesn't use SSH for bootstrapping nodes.
Installs only the minimal components to bootstrap a control plane and workers.
Supports control planes on EC2 instances.
Experimental EKS support

Compatibility with Cluster API and Kubernetes Versions

This provider's versions are compatible with the following versions of Cluster API:

	Cluster API v1alpha1 (v0.1)	Cluster API v1alpha2 (v0.2)	Cluster API v1alpha3 (v0.3)
AWS Provider v1alpha1 (v0.2)	✓
AWS Provider v1alpha1 (v0.3)	✓
AWS Provider v1alpha2 (v0.4)		✓
AWS Provider v1alpha3 (v0.5)			✓
AWS Provider v1alpha3 (v0.6)			✓

This provider's versions are able to install and manage the following versions of Kubernetes:

	Kubernetes 1.13	Kubernetes 1.14	Kubernetes 1.15	Kubernetes 1.16	Kubernetes 1.17	Kubernetes 1.18	Kubernetes 1.19
AWS Provider v1alpha1 (v0.2)	✓	✓	✓
AWS Provider v1alpha1 (v0.3)	✓	✓	✓
AWS Provider v1alpha2 (v0.4)		✓	✓	✓	✓
AWS Provider v1alpha3 (v0.5)			✓	✓	✓	✓	✓
AWS Provider v1alpha3 (v0.6)			✓	✓	✓	✓	✓

Each version of Cluster API for AWS will attempt to support two Kubernetes versions; e.g., Cluster API for AWS v0.2 may support Kubernetes 1.13 and Kubernetes 1.14.

NOTE: As the versioning for this project is tied to the versioning of Cluster API, future modifications to this policy may be made to more closely align with other providers in the Cluster API ecosystem.

Kubernetes versions with published AMIs

Note: These AMIs are not updated for security fixes and it is recommended to always use the latest patch version for the Kubernetes version you wish to run. For production-like environments, it is highly recommended to build and use your own custom images.

Kubernetes minor version	Kubernetes full version
v1.16	v1.16.0
	v1.16.1
	v1.16.2
	v1.16.3
	v1.16.4
	v1.16.5
	v1.16.6
	v1.16.7
	v1.16.8
	v1.16.9
	v1.16.14
	v1.16.15
v1.17	v1.17.0
	v1.17.1
	v1.17.2
	v1.17.3
	v1.17.4
	v1.17.5
	v1.17.11
	v1.17.12
v1.18	v1.18.0
	v1.18.1
	v1.18.2
	v1.18.8
	v1.18.9
v1.19	v1.19.0
	v1.19.1
	v1.19.2

Getting involved and contributing

Are you interested in contributing to cluster-api-provider-aws? We, the maintainers and community, would love your suggestions, contributions, and help! Also, the maintainers can be contacted at any time to learn more about how to get involved.

In the interest of getting more new people involved we tag issues with good first issue. These are typically issues that have smaller scope but are good ways to start to get acquainted with the codebase.

We also encourage ALL active community participants to act as if they are maintainers, even if you don't have "official" write permissions. This is a community effort, we are here to serve the Kubernetes community. If you have an active interest and you want to get involved, you have real power! Don't assume that the only people who can get things done around here are the "maintainers".

We also would love to add more "official" maintainers, so show us what you can do!

This repository uses the Kubernetes bots. See a full list of the commands here.

Build the images locally

If you want to just build the CAPA containers locally, run

	REGISTRY=docker.io/my-reg make docker-build

Tilt-based development environment

We have support for using Tilt for rapid iterative development. Please visit the Cluster API documentation on Tilt for information on how to set up your development environment. Additionally, you must also include your base64 encoded AWS credentials in your tilt-settings.json file or you will not be able to deploy this provider.

make clusterawsadm
export AWS_REGION=<your desired region
./bin/clusterawsadm alpha bootstrap encode-aws-credentials
Copy the output containing the base64 encoded credentials and add it to your tilt-settings.json file like this:

{
  "allowed_contexts": ["kind-kind"],
  "default_registry": "your registry here",
  "provider_repos": ["../cluster-api-provider-aws"],
  "enable_providers": ["aws"],
  "kustomize_substitutions": {
    "AWS_B64ENCODED_CREDENTIALS": "put your encoded credentials here"
  }
}

Implementer office hours

Maintainers hold office hours every two weeks, with sessions open to all developers working on this project.

Office hours are hosted on a zoom video chat every other Monday at 10:00 (Pacific) / 13:00 (Eastern) / 18:00 (Europe/London), and are published on the Kubernetes community meetings calendar.

Other ways to communicate with the contributors

Please check in with us in the #cluster-api-aws channel on Slack.

Github issues

Bugs

If you think you have found a bug please follow the instructions below.

Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
Get the logs from the cluster controllers. Please paste this into your issue.
Open a new issue.
Remember that users might be searching for your issue in the future, so please give it a meaningful title to help others.
Feel free to reach out to the cluster-api community on the kubernetes slack.

Tracking new features

We also use the issue tracker to track features. If you have an idea for a feature, or think you can help kops become even more awesome follow the steps below.

Open a new issue.
Remember that users might be searching for your issue in the future, so please give it a meaningful title to help others.
Clearly define the use case, using concrete examples. EG: I type this and cluster-api-provider-aws does that.
Some of our larger features will require some design. If you would like to include a technical design for your feature please include it in the issue.
After the new feature is well understood, and the design agreed upon, we can start coding the feature. We would love for you to code it. So please open up a WIP (work in progress) pull request, and happy coding.

“Amazon Web Services, AWS, and the “Powered by AWS” logo materials are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries."

shysank/cluster-api-provider-aws