Context:

During the ClusterAPI Weekly meeting on 6 May 2020, I wondered why no capd-controller-manager:v0.3.0 image was pushed to the gcr.io/staging-capi-docker registry (see the discussion).

@dlipovetsky told me that the "dev experience" with CAPD had changed as detailed in clusterctl/developers.html and that the image isn’t being published right now.

User Story

As a developer or operator, I would like to be able to very quickly get started using CAPI + CAPD. Right now, a newcomer to the project has to go through quite a lot of steps (as detailed in clusterctl/developers.html) including a docker build that end up taking quite a lot of time to build (like any other Kubernetes controller) and the kind load also takes a few seconds.

This user story only addresses the docker build + kind load. The developer or operator willing to take a look at ClusterAPI using CAPD will still have to go through the remaining steps in clusterctl/developers.html.

Detailed Description

I wish we could have a new OCI image capd-controller-manager pushed to gcr.io/staging-capi-docker whenever a tag is created in the cluster-api project. My guess is that it could be done as part of CI?

Related: #2738

I'd be happy to help! (in what direction should I look at?)

Update: see the 27 May 2020 weekly meeting recording (at 17:18) where this issue is discussed