Cluster-api: Homebrew formula for clusterctl

[vincepri]

Clusterctl can live on its own. To ease adoption, we can publish a formula to Homebrew with each release, the process should be as automated as possible.

See https://github.com/kubernetes-sigs/kind/issues/88 for examples.

/kind feature
/milestone Next
/priority backlog
/help

[k8s-ci-robot]

@vincepri:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Clusterctl can live on its own. To ease adoption, we can publish a formula to Homebrew with each release, the process should be as automated as possible.

See https://github.com/kubernetes-sigs/kind/issues/88 for examples.

/kind feature
/milestone Next
/priority backlog
/help

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/test-infra repository.

[detiber]

If this would require credentials to be managed for an account for publishing, I'm not sure how much help wanted applies to this issue.

[randomvariable]

Is krew a more suitable option? Has the advantage of better cross-platformability.

[detiber]

If we are willing to refactor into a kubectl plugin, I think so

[voor]

After reviewing the design docs for clusterctl this part stands out:

Enable provider specific deployment templates, or flavors, to end users. E.g. dev, test, prod, etc.

For that reason, it either makes sense to pull that functionality specifically into a kubectl plugin, or look at clusterctl itself as a kubectl plugin.

If the intended audience is just cluster admins and individuals upgrading provider components, then a single cli for that makes sense, but if "end users" are also meant to self-provision or create their own clusters (which also makes sense) then they're familiar with the kubectl experience.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[vincepri]

/lifecycle frozen

It'd be great to still do this if we have some time, we can also offer one for Linux.

[evalsocket]

/assign @evalsocket

@detiber Hey, We need to add an index for the plugin. You can publish any cli tool as a kubectl plugin. Check https://krew.sigs.k8s.io/docs/developer-guide/.
@vincepri I am doing it. Can we use goreleaser for publishing the brew package?