Update kube-vip to v0.8.0

[jisnardo]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Keep kube-vip updated

Which issue(s) this PR fixes:

Fixes # version

Special notes for your reviewer:

Keep kube-vip updated

Does this PR introduce a user-facing change?:

Update kube-vip to v0.8.0

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jisnardo / name: Jorge Isnardo Altamirano (e57e958, def88b2, 001df23, 9bb3816, 40cbdce, 537891a, a09c73a)

[k8s-ci-robot]

Welcome @jisnardo!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. 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/kubespray 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 @jisnardo. 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.

[mzaian]

Hello @jisnardo

Thanks a lot for the PR. Did you check If you need to update the manifests Ref: https://github.com/kube-vip/kube-vip/blob/v0.8.0/pkg/kubevip/config_generator.go

/ok-to-test

[jisnardo]

Hi @mzaian, now yes Thanks.

[jisnardo]

/retest-required

[jisnardo]

/retest

[jisnardo]

/retest

[jisnardo]

@mzaian what about this? packet_centos7-flannel-addons-ha https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/6783243276

[mzaian]

@mzaian what about this? packet_centos7-flannel-addons-ha https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/6783243276

The error are visible here

TASK [kubernetes/node : Kube-vip | Write static pod] ***************************
task path: /builds/kargo-ci/kubernetes-sigs-kubespray/roles/kubernetes/node/tasks/loadbalancer/kube-vip.yml:9
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'kube_vip_svc_leasename' is undefined. 'kube_vip_svc_leasename' is undefined
fatal: [instance-1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'kube_vip_svc_leasename' is undefined. 'kube_vip_svc_leasename' is undefined"}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'kube_vip_svc_leasename' is undefined. 'kube_vip_svc_leasename' is undefined
fatal: [instance-2]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'kube_vip_svc_leasename' is undefined. 'kube_vip_svc_leasename' is undefined"}

[jisnardo]

/lgtm

[k8s-ci-robot]

@jisnardo: you cannot LGTM your own PR.

In response to this:

/lgtm

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-sigs/prow repository.

[jisnardo]

Now ready @mzaian, thanks

[mzaian]

/cc @VannTen @yankay

[yankay]

Thanks @mzaian
/approve

[mzaian]

/lgtm

[jisnardo]

/retest-required

[VannTen]

I'm not sure how we can override the status, because the CI is green, it's only the integration to gitlab which was broken due to token expiration and does not appear to be able to unstuck itself... 🤔

[VannTen]

/override kubespray-ci/pipeline

[mzaian]

@jisnardo Could you please rebase your branch.

[k8s-ci-robot]

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found 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-sigs/prow repository.

[jisnardo]

@mzaian done.

[mzaian]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jisnardo, mzaian, yankay

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 [mzaian,yankay]

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