[Snyk] Security upgrade ubuntu from latest to 22.04

[rajeshfrontline]

This PR was automatically created by Snyk using the credentials of a real user.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

• Dockerfile

We recommend upgrading to ubuntu:22.04, as this image has only 11 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity	Issue	Exploit Maturity
	Out-of-bounds Read SNYK-UBUNTU2204-E2FSPROGS-2801319	No Known Exploit
	CVE-2021-46828 SNYK-UBUNTU2204-LIBTIRPC-2956571	No Known Exploit
	CVE-2021-46828 SNYK-UBUNTU2204-LIBTIRPC-2956571	No Known Exploit
	Inadequate Encryption Strength SNYK-UBUNTU2204-OPENSSL-2941376	No Known Exploit
	Improper Verification of Cryptographic Signature SNYK-UBUNTU2204-PERL-2789081	No Known Exploit

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[spectro-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rajeshfrontline
To complete the pull request process, please assign abhinavnagaraj
You can assign the PR to them by writing /assign @abhinavnagaraj in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[spectro-prow]

Welcome @rajeshfrontline! It looks like this is your first PR to spectrocloud/cluster-api-provider-vsphere-static-ip 🎉

[spectro-prow]

Hi @rajeshfrontline. Thanks for your PR.

I'm waiting for a spectrocloud 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.