NO-JIRA:reconcile azure creds to a fixed secret in hcp namespace

[Patryk-Stefanski]

What this PR does / why we need it:
This is blocking 4.17 aks e2e as it cannot create an HC because the reconcile of cloud credentials is blocking progression as it is unable to find the -cloud-credentials secret in HCP NS as made in the HC NS. In newer releases, we use a fixed secret in the HCP namespace instead so this is copying that behavior.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[openshift-ci-robot]

@Patryk-Stefanski: This pull request explicitly references no jira issue.

In response to this:

What this PR does / why we need it:
This is blocking 4.17 aks e2e as it cannot create an HC because the reconcile of cloud credentials is blocking progression as it is unable to find the -cloud-credentials secret in HCP NS as made in the HC NS. In newer releases, we use a fixed secret in the HCP namespace instead so this is copying that behavior.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

[Patryk-Stefanski]

/test e2e-aks

[openshift-ci]

@Patryk-Stefanski: The following test 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/e2e-aks	5fef068	link	false	/test e2e-aks

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.

[jparrill]

Hey @Patryk-Stefanski It's not usual to put a PR against 4.17 directly, is this blocking you? It's there any way to use the typical backport flow to follow in this case?

[Patryk-Stefanski]

It's not usual to put a PR against 4.17 directly, is this blocking you? It's there any way to use the typical backport flow to follow in this case?

This is one of the things that is causing the 4.17 aks e2e to fail, there is a change in 4.18 that fixes this but it requires a manual backport of a few different PRs, I was hoping this would be a quick fix.

We might not need a 4.17 aks e2e, @bryan-cox any update on that ? We can close this PR if we don't need 4.17.

[bryan-cox]

It's not usual to put a PR against 4.17 directly, is this blocking you? It's there any way to use the typical backport flow to follow in this case?

This is one of the things that is causing the 4.17 aks e2e to fail, there is a change in 4.18 that fixes this but it requires a manual backport of a few different PRs, I was hoping this would be a quick fix.

We might not need a 4.17 aks e2e, @bryan-cox any update on that ? We can close this PR if we don't need 4.17.

@Patryk-Stefanski no update right now