Create Release Targets

[anusha94]

Create make targets that will be used for release activities

• host-agent-binary
• infrastructure-components.yaml
• cluster-template.yaml
• metadata.yaml
• [ ] byoh controller image (build and push)
• [ ] imgpkg k8s bundle (build and push)

[jamiemonserrate]

Can we ensure that when we publish the host-agent binary, it is an executable binary? (that is the exec bit is set)

[anusha94]

/unassign

[anusha94]

fyi - I am working on build and push controller image task

[anusha94]

In BYOH, currently all images and installer bundles are pushed to Harbor registry. To push to this registry, we need to be in VMware's corporate network. Automating the push via GitHub Action's runner may become complicated as we will have to directly hit the registry's IP and store this IP as a secret.
We will migrate to k-sigs soon and hope to leverage Prow's capability to push to gcr.io just like other providers. Closing this issue for now.

[anusha94]

Can we ensure that when we publish the host-agent binary, it is an executable binary? (that is the exec bit is set)

@jamiemonserrate when we build the binary, it is indeed executable. But when we download the binary, the exec bit is not set. Same goes for any other binary we download. See clusterctl install or kubectl install

TIL - https://unix.stackexchange.com/questions/82578/why-is-that-when-i-download-a-binary-from-the-web-it-doesnt-have-executable-per

Let me know if you had something else to try out. Otherwise, we are pretty much done with this issue.

[jamiemonserrate]

That makes sense. Not sure what I was thinking when I wrote

Can we ensure that when we publish the host-agent binary, it is an executable binary? (that is the exec bit is set).

Fair enough.