Update to Cluster API 1.5.3

[elmiko]

What this PR does / why we need it:

update the provider to use CAPI 1.5.3

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
fixes #93

Special notes for your reviewer:

Release notes:

Updated for Cluster API version 1.5.3

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elmiko

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

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

[elmiko]

it took some modifications, but i've updated everything to use kube 1.27 and capi 1.5, here is the resultant cluster that was created after i applied cni

mike@capivm:~/cluster-api-provider-kubemark$ kubectl --kubeconfig=/tmp/km.kubeconfig get nodes
NAME                        STATUS     ROLES           AGE     VERSION
km-cp-control-plane-dwl5z   NotReady   control-plane   6m8s    v1.27.3
km-wl-kubemark-md-0-9slzx   Ready      <none>          5m54s   v1.27.3
km-wl-kubemark-md-0-b4gd7   Ready      <none>          5m55s   v1.27.3
km-wl-kubemark-md-0-hsgzx   Ready      <none>          5m54s   v1.27.3
km-wl-kubemark-md-0-jm4n6   Ready      <none>          5m55s   v1.27.3
mike@capivm:~/cluster-api-provider-kubemark$ kubectl --kubeconfig=/tmp/km.kubeconfig get pods -A
NAMESPACE     NAME                                                READY   STATUS     RESTARTS   AGE
kube-system   calico-kube-controllers-784cc4bcb7-mcjrf            1/1     Running    0          44s
kube-system   calico-node-hbbpt                                   0/1     Init:0/3   0          44s
kube-system   calico-node-mbjrr                                   0/1     Init:0/3   0          44s
kube-system   calico-node-sxjh6                                   0/1     Init:0/3   0          44s
kube-system   calico-node-wnlbc                                   0/1     Init:0/3   0          44s
kube-system   calico-node-zlckl                                   0/1     Init:0/3   0          44s
kube-system   coredns-5d78c9869d-9j5bm                            1/1     Running    0          6m3s
kube-system   coredns-5d78c9869d-cqdvd                            1/1     Running    0          6m3s
kube-system   etcd-km-cp-control-plane-dwl5z                      1/1     Running    0          6m11s
kube-system   kube-apiserver-km-cp-control-plane-dwl5z            1/1     Running    0          6m11s
kube-system   kube-controller-manager-km-cp-control-plane-dwl5z   1/1     Running    0          6m11s
kube-system   kube-proxy-7h6n7                                    1/1     Running    0          5m58s
kube-system   kube-proxy-fn5qd                                    1/1     Running    0          5m58s
kube-system   kube-proxy-p6lgs                                    1/1     Running    0          5m58s
kube-system   kube-proxy-tfprt                                    1/1     Running    0          6m3s
kube-system   kube-proxy-wszl8                                    1/1     Running    0          5m59s
kube-system   kube-scheduler-km-cp-control-plane-dwl5z            1/1     Running    0          6m11s

[killianmuldoon]

/lgtm

/hold

(not sure if you squash commits on this repo, but feel free to unhold if it's okay)

[elmiko]

thanks @killianmuldoon !

we haven't been squashing commits here, not for any specific reason other than perhaps laziness and the testing nature of this provider.

/hold cancel