Skip to content
Branch: master
Find file History

Files

Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
api/v1alpha3 capd: Make ready an optional field Mar 6, 2020
cloudinit tests: move NewWithT(t) to inside the t.Run where applicable Mar 27, 2020
config dependencies: update controller-runtime to v0.5.2 and controller-tool… Mar 27, 2020
controllers test/tests: standardize gomega imports Mar 16, 2020
docker Do not kubeadm reset in capd any more Mar 10, 2020
docs Remove dependency on kind v0.5.1 Jan 17, 2020
e2e Adds coredns upgrade validations to upgrade e2e tests Mar 27, 2020
examples Add clusterName to machine spec Dec 12, 2019
hack dependencies: update controller-runtime to v0.5.2 and controller-tool… Mar 27, 2020
scripts author Chuck Ha <chuckh@vmware.com> 1560208528 -0400 Oct 10, 2019
third_party/forked Use a better loadbalancer for capd Feb 25, 2020
.gitignore capd: make setting provider ID re-entrant Mar 6, 2020
Dockerfile 🏃 speed up e2e image builds Mar 12, 2020
Dockerfile.dev go: bump go to 1.13.8 Mar 2, 2020
LICENSE author Chuck Ha <chuckh@vmware.com> 1560208528 -0400 Oct 10, 2019
Makefile Refactor upgrade tests Mar 26, 2020
OWNERS 🏃 Refactor OWNERS files throughout the repo Mar 2, 2020
PROJECT docker fixes for v1a3 Dec 10, 2019
README.md Implements e2e tests for CAPD using the new framework Nov 14, 2019
go.mod dependencies: update controller-runtime to v0.5.2 and controller-tool… Mar 27, 2020
go.sum dependencies: update controller-runtime to v0.5.2 and controller-tool… Mar 27, 2020
main.go Seed the random number generator Mar 25, 2020

README.md

Cluster API Provider Docker (CAPD)

CAPD is a reference implementation of an infrastructure provider for the Cluster API project using Docker.

This is one out of three components needed to run a Cluster API management cluster.

For a complete overview, please refer to the documentation available here which uses CAPD as an example infrastructure provider.

CAPD Goals

  • To be a the reference implementation of an infrastructure provider.
  • The code is highly trusted and used in testing of ClusterAPI.
  • This provider can be used as a guide for developers looking to implement their own infrastructure provider.

End-to-end testing

In order to test your local changes, go to the top level directory of this project, cluster-api/ and run make -C test/infrastructure/docker test-e2e to run the test suite.

This make target will build an image based on the local source code and use that image during testing.

You can’t perform that action at this time.