✨ Force rebuild of tilt-prepare

[johannesfrey]

What this PR does / why we need it:
This PR forces a rebuild of the tilt-prepare binary when running tilt up in order to incorporate code changes. Recent example: The cert-manager repo moved to another location but this change did not reflect in tilt-prepare when it was already built beforehand.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #6077

Signed-off-by: Johannes Frey [email protected]

_{Johannes Frey <[email protected]>, Daimler TSS GmbH (Provider Information)}

[k8s-ci-robot]

Welcome @johannesfrey!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @johannesfrey. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[sbueringer]

/ok-to-test
/lgtm

Thank you very much!

I know we are changing tilt-prepare only once in a while, but there are some change like the cert-manager thing or #6079. Whenever we have a change like this, it becomes an additional hurdle for folks who are not familiar with the details of our tilt setup because they are confronted with some strange errors.

So huge +1 from my side :)

P.S. Now that we are sure that tilt-prepare is always up-to-date, we could add version checks for kustomize/envsubst/helm in tilt-prepare which can produce user-understandable errors. But I would only consider this if we run into compatibility issues there in the future.

[enxebre]

/lgtm

[fabriziopandini]

@johannesfrey thanks for your first CAPI PR! 🥳
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment