OCPBUGS-78118: Add delete permission for Azure load balancers in credentials request

[RadekManak]

No description provided.

[openshift-ci-robot]

@RadekManak: This pull request references Jira Issue OCPBUGS-78118, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 609f28e8-3194-4a1b-bbb8-50fda8510baa

📥 Commits

Reviewing files that changed from the base of the PR and between b108246 and c6f1319.

📒 Files selected for processing (1)

• manifests/0000_26_cloud-controller-manager-operator_14_credentialsrequest-azure.yaml

---

Walkthrough

Two Azure permissions are added to the CredentialsRequest manifest file for the cloud-controller-manager-operator. The additions extend the spec.providerSpec.permissions list with Microsoft.Network/loadBalancers/delete and Microsoft.Network/privatelinkservices/privateEndpointConnections/delete capabilities.

Changes

Cohort / File(s)	Summary
Azure CredentialsRequest Permissions manifests/0000_26_cloud-controller-manager-operator_14_credentialsrequest-azure.yaml	Added two Azure permissions: Microsoft.Network/loadBalancers/delete and Microsoft.Network/privatelinkservices/privateEndpointConnections/delete to the spec.providerSpec.permissions list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

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

Details

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

[RadekManak]

/jira refresh

[openshift-ci-robot]

@RadekManak: This pull request references Jira Issue OCPBUGS-78118, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@RadekManak: all tests passed!

Full PR test history. Your PR dashboard.

Details

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