killianmuldoon

@hiromu-a5a Good to see somebody picking up this work! I just wanted to mention that some parts of this - if they involve changes to the MachineDeployment controller - might...

@mjnovice - nobody has followed up on this as a general case as far as I know. Have you run into this issue?

>Any way we can circumvent this ? Circumvention for this is to use a github token, which should get rid of most of the rate limiting, or else use a...

/close Thanks for pointing this out @adityabhatia

I think this should be closed in favor of a solution on the CAPI side - there's a related issue here: https://github.com/kubernetes-sigs/cluster-api/issues/5510

/close I'm taking a look at restructuring some of the test directory - starting with https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/2251. Will take this into account when thinking about consolidating existing tests.

/triage accepted Sounds reasonable to me. /help

> A kubeconfig flag Maybe consider `--into-kubeconfig` to make the behaviour clear.

/reopen I'll a test to figure out the current state of this on the CAPI repo. /cc @nikhita

Testing this on https://github.com/kubernetes-sigs/cluster-api/pull/8844 CAPI has three actions here which are all failing on the PR: 1) PR Verify 2) Lint 3) Check markdown links Currently it looks like `/retest`...