chore: update AzCNI to new installer image

[rbtr]

What type of PR is this?
/kind cleanup

What this PR does / why we need it: Migrates to new installer image for AzCNI. Incidentally upgrades the AzCNI version.

See Azure/azure-container-networking#2333

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 #

Special notes for your reviewer:

TODOs:

Release note:

Update AzCNI to v1.5.16

[k8s-ci-robot]

@rbtr: The label(s) kind/chore cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?
/kind chore

What this PR does / why we need it: Migrates to new installer image for AzCNI. Incidentally upgrades the AzCNI version.

See Azure/azure-container-networking#2333

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 #

Special notes for your reviewer:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

Update AzCNI to v1.5.14

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.

[k8s-ci-robot]

Welcome @rbtr!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-azure 🎉. 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/cluster-api-provider-azure 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 @rbtr. 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.

[mboersma]

/ok-to-test

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (388398e) 60.03% compared to head (6f3cc09) 60.45%.
Report is 74 commits behind head on main.

Files	Patch %	Lines
exp/controllers/helpers.go	33.33%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4315      +/-   ##
==========================================
+ Coverage   60.03%   60.45%   +0.41%     
==========================================
  Files         192      191       -1     
  Lines       19297    19195     -102     
==========================================
+ Hits        11585    11604      +19     
+ Misses       7075     6947     -128     
- Partials      637      644       +7     

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

[CecileRobertMichon]

/retest

@rbtr the Azure CNI e2e test failed, PTAL

[rbtr]

waiting on Azure/azure-container-networking#2417 then will bump this again to resolve

[rbtr]

updated actually needs a newer image tagged and published with an unreleased fix, will update again

[rbtr]

/retest

[rbtr]

/kind cleanup

[mboersma]

/lgtm

I wish y`all had copied it, then there only would have been one thing to update 🥲

Is this still an approach we should take in CAPZ? If so, let's open an issue with more specific detail.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 77e42193155243dfcdc253aaf69471a88c4366e7

[CecileRobertMichon]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

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 [CecileRobertMichon]

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