OCPBUGS-42325: Set separate secrets for file and disk config on HyperShift

[bryan-cox]

Set separate secrets for file and disk authentication config for Azure. Previously, these two components were reusing the same configuration as cloud provider.

[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

[jsafrane]

It's a good idea to separate these secrets, is there a corresponding hypershift PR that creates those secrets?

[bryan-cox]

It's a good idea to separate these secrets, is there a corresponding hypershift PR that creates those secrets?

Hey @jan--f - there isn't a PR at the moment but there will be in the near future. HyperShift would be responsible for creating/reconciling that within the HCP namespace.

[bryan-cox]

I opened openshift/hypershift#4861 for now to correlate to this PR.

[bryan-cox]

/retest

[openshift-ci-robot]

@bryan-cox: This pull request references HOSTEDCP-2033 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 only the "4.18.0" version, but multiple target versions were set.

In response to this:

Set separate secrets for file and disk authentication config for Azure. Previously, these two components were reusing the same configuration as cloud provider.

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.

[bryan-cox]

/retest

[openshift-ci-robot]

@bryan-cox: This pull request references Jira Issue OCPBUGS-42325, 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.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

In response to this:

Set separate secrets for file and disk authentication config for Azure. Previously, these two components were reusing the same configuration as cloud provider.

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]

@bryan-cox: 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/security	12d3bc3	link	false	/test security
ci/prow/e2e-azurestack-csi	12d3bc3	link	false	/test e2e-azurestack-csi

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.

[jsafrane]

/lgtm
/approve

[Phaow]

/label docs-approved
/label px-approved
/label qe-approved

[openshift-ci-robot]

@bryan-cox: This pull request references Jira Issue OCPBUGS-42325, which is valid.

3 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

Set separate secrets for file and disk authentication config for Azure. Previously, these two components were reusing the same configuration as cloud provider.

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.

[Phaow]

Will do some intergration test with hypershift QE guys later when the configuration of cluster could be created.

[jsafrane]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox, jsafrane

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

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