feat: add new release process

This PR will move to publishing `bootstrap-components.yaml` and
`metdata.yaml` upon tagging a release so that clusterctl can consume
them.

Signed-off-by: Spencer Smith <[email protected]>

Author: rsmitty

Dockerfile

@@ -40,9 +40,11 @@ ARG TAG
 RUN cd config/manager \
   && kustomize edit set image controller=${REGISTRY_AND_USERNAME}/${NAME}:${TAG} \
   && cd - \
-  && kubectl kustomize config/default >/release.yaml
+  && kubectl kustomize config/default >/bootstrap-components.yaml \
+  && cp config/metadata/metadata.yaml /metadata.yaml
 FROM scratch AS release
-COPY --from=release-build /release.yaml /release.yaml
+COPY --from=release-build /bootstrap-components.yaml /bootstrap-components.yaml
+COPY --from=release-build /metadata.yaml /metadata.yaml
 
 FROM build AS binary
 RUN --mount=type=cache,target=/root/.cache/go-build GOOS=linux go build -ldflags "-s -w" -o /manager

README.md

@@ -15,9 +15,9 @@ There are a few corequisites and assumptions that go into using this project:
 ## Building and Installing
 
 This project can be built simply by running `make release` from the root directory.
-Doing so will create a file called `_out/release.yaml`.
+Doing so will create a file called `_out/bootstrap-components.yaml`.
 If you wish, you can tweak settings by editing the release yaml.
-This file can then be installed into your management cluster with `kubectl apply -f _out/release.yaml`.
+This file can then be installed into your management cluster with `kubectl apply -f _out/bootstrap-components.yaml`.
 
 Note that CABPT should be deployed as part of a set of controllers for Cluster API.
 You will need at least the upstream CAPI components and an infrastructure provider for v1alpha2 CAPI capabilities.

config/metadata/metadata.yaml

@@ -0,0 +1,6 @@
+apiVersion: clusterctl.cluster.x-k8s.io/v1alpha3
+kind: Metadata
+releaseSeries:
+- major: 0
+  minor: 1
+  contract: v1alpha2