chore(deps): update gsoci.azurecr.io/giantswarm/kube-vip docker tag to v0.8.3

[renovate]

This PR contains the following updates:

Package	Update	Change
gsoci.azurecr.io/giantswarm/kube-vip	patch	v0.8.2 -> v0.8.3

Trigger E2E tests:

/run cluster-test-suites

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-vsphere-286-cluster-test-suitestrtj7
Commit SHA	8faeacd
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[vxav]

/run cluster-test-suites

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-vsphere-286-cluster-test-suites2w7ns
Commit SHA	f05dd91
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[github-actions]

There were differences in the rendered Helm template, please check! ⚠️

Output

=== Differences when rendered with values file helm/cluster-vsphere/ci/test-wc-values.yaml ===

/stringData/content  (v1/Secret/release-name-kubevip-pod)
  ± value change in multiline text (one insert, one deletion)
    -     image: gsoci.azurecr.io/giantswarm/kube-vip:v0.8.2
    +     image: gsoci.azurecr.io/giantswarm/kube-vip:v0.8.3