🌱 Better verbose logging on override path

[ryjogo]

What this PR does / why we need it:

Aids troubleshooting when dealing with overrides, at least it helped me when looking at #10179

/area clusterctl

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ryjogo / name: Ryan Gough (596f59a, b036df8)

[k8s-ci-robot]

Welcome @ryjogo!

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 @ryjogo. 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.

[chrischdi]

/ok-to-test

Change looks good to me. Could you provide a sample how the log looks like?

[ryjogo]

/ok-to-test

Change looks good to me. Could you provide a sample how the log looks like?

Oh, sure:

➜  bin/clusterctl generate cluster capi-test \
    --kubeconfig ~/.kube/kind \
    --config ~/.cluster-api/clusterctltest.yaml \
    --infrastructure vsphere \
    --kubernetes-version v1.29.0 \
    --control-plane-machine-count 1 \
    --worker-machine-count 3 -v5 > /dev/null
    
Using configuration File="/Users/rgo/.cluster-api/clusterctltest.yaml"
Overrides SearchFile="/Users/rgo/.config/cluster-api/overrides/infrastructure-vsphere/v1.9.0/cluster-template.yaml" Provider="infrastructure-vsphere" Version="v1.9.0"
Fetching File="cluster-template.yaml" Provider="vsphere" Type="InfrastructureProvider" Version="v1.9.0"
Using configuration File="/Users/rgo/.cluster-api/clusterctltest.yaml"

[chrischdi]

Small cahnge for the log message, otherwise looks good and I think it provides great value when one hits the issue of override does not get used 👍

[ryjogo]

Yeah, that's more descriptive.

[chrischdi]

Could you please rebase the PR? We should not have merge commits on the PR :-)

When testing, prow automatically rebases before doing testing.

[ryjogo]

Hope that did it... apologies.

[chrischdi]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f837127df0d9af9e6d79acf25eed4086987a7dbe

[vincepri]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

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 [vincepri]

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