OADP-3340: Support the standardized Azure Identity configuration flow via OLM and CCO for OADP

[shubham-pampattiwar]

No description provided.

[openshift-ci-robot]

@shubham-pampattiwar: This pull request references OADP-3340 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

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.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shubham-pampattiwar

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 [shubham-pampattiwar]

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

[shubham-pampattiwar]

Tested the CCO workflow for Azure credentials request on OCP 4.15 pre-released Azure identity cluster, it worked fine. Now need to check whether the Velero-plugin-for-microsoft-azure supports authentication via this method.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-merge-robot]

PR needs rebase.

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.

[kaovilai]

still planned for 1.4 per jira

/remove-lifecycle stale

[openshift-ci]

@shubham-pampattiwar: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/4.16-ci-index	9732ad0	link	true	/test 4.16-ci-index
ci/prow/4.16-e2e-test-aws	9732ad0	link	true	/test 4.16-e2e-test-aws
ci/prow/4.16-e2e-test-kubevirt-aws	9732ad0	link	true	/test 4.16-e2e-test-kubevirt-aws
ci/prow/4.16-images	9732ad0	link	true	/test 4.16-images
ci/prow/4.15-e2e-test-kubevirt-aws	9732ad0	link	true	/test 4.15-e2e-test-kubevirt-aws
ci/prow/4.15-images	9732ad0	link	true	/test 4.15-images
ci/prow/4.15-ci-index	9732ad0	link	true	/test 4.15-ci-index
ci/prow/4.15-e2e-test-aws	9732ad0	link	true	/test 4.15-e2e-test-aws

Full PR test history. Your PR dashboard.

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale