CAPV: use v1.9 milestone on main

[sbueringer]

We're going to release CAPV v1.8 today. So as we don't fast-forward the release-1.8 branch anymore we should start applying the v1.9 milestone on main

Signed-off-by: Stefan Büringer [email protected]

Part of kubernetes-sigs/cluster-api-provider-vsphere#2175

[sbueringer]

/assign @killianmuldoon @chrischdi
for CAPV

/assign @dims
for approval

[chrischdi]

/lgtm
/approve

[killianmuldoon]

/lgtm
/approve

[dims]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi, dims, killianmuldoon, sbueringer

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:

• config/OWNERS [dims]

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

[k8s-ci-robot]

@sbueringer: Updated the plugins configmap in namespace default at cluster test-infra-trusted using the following files:

• key plugins.yaml using file config/prow/plugins.yaml

In response to this:

We're going to release CAPV v1.8 today. So as we don't fast-forward the release-1.8 branch anymore we should start applying the v1.9 milestone on main

Signed-off-by: Stefan Büringer [email protected]

Part of kubernetes-sigs/cluster-api-provider-vsphere#2175

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.