Optimize go build caching in `release-binary` make target

[Dhairya-Arora01]

The release-binary Makefile target currently uses /tmp/ as the GOCACHE directory inside the Docker container, which means the build cache is discarded after every run. This results in slower builds since Go has to recompile everything from scratch each time.

The make target release-binaries build the clusterctl binary for each architecture by calling the release-binary target. Therefore, the same go packages are installed each and every time and recompilation from scratch occurs every time which is bit inefficient.

Changes proposed:

• Set GOCACHE to /go/build-cache/ instead of /tmp/
• Mount the host's GOMODCACHE into the container at /go/pkg/mod to reuse downloaded modules.
• Mount the host's GOCACHE into the container at /go/build-cache to persist the build cache across runs.

These volume mounts allow the Docker build to leverage caches from the host machine, significantly speeding up incremental builds.

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.