🌱 flavorgen: bump kubevip to v0.6.4 and import from file

[chrischdi]

What this PR does / why we need it:

• Bumps kube-vip to v0.6.4
• Adjusts flavorgen to import kube-vip.yaml from file and add required changes on top.

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 #

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b230286) 64.94% compared to head (d847354) 64.62%.
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2655      +/-   ##
==========================================
- Coverage   64.94%   64.62%   -0.32%     
==========================================
  Files         118      118              
  Lines        8580     8580              
==========================================
- Hits         5572     5545      -27     
- Misses       2582     2602      +20     
- Partials      426      433       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fabriziopandini]

nice, just one nit from my side

[sbueringer]

/test ?

[k8s-ci-robot]

@sbueringer: The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-vsphere-conformance-ci-latest-main
• /test pull-cluster-api-provider-vsphere-conformance-main
• /test pull-cluster-api-provider-vsphere-e2e-full-main
• /test pull-cluster-api-provider-vsphere-e2e-main
• /test pull-cluster-api-provider-vsphere-test-integration-main
• /test pull-cluster-api-provider-vsphere-test-main
• /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-vsphere-apidiff-main

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-vsphere-apidiff-main
• pull-cluster-api-provider-vsphere-e2e-main
• pull-cluster-api-provider-vsphere-test-integration-main
• pull-cluster-api-provider-vsphere-test-main
• pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test ?

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]

Thx!

/lgtm
/approve

/test pull-cluster-api-provider-vsphere-conformance-main
/test pull-cluster-api-provider-vsphere-e2e-full-main

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b93430c4bd76eca047754bb5a8b6b80578cfc013

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

• OWNERS [sbueringer]

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

[sbueringer]

@chrischdi PTAL. Maybe a first flake from the new claim IP code

[chrischdi]

@chrischdi PTAL. Maybe a first flake from the new claim IP code

xref fix: #2663

[chrischdi]

/retest

[k8s-ci-robot]

@chrischdi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-vsphere-apidiff-main	d847354	link	false	/test pull-cluster-api-provider-vsphere-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.