CNV-37629: Keep name when configuring existing SSH key in same namespace

[pcbailey]

📝 Description

When configuring an existing SSH secret for the namespace in which that secret resides in the "Manage SSH keys" section the UI displays the secret name with a randomly generated suffix. In actuality, that secret wasn't created and doesn't exist. This can be demonstrated by navigating away from that screen and returning to it. Upon doing so "Not configured" will be displayed for that namespace instead of the generated secret name.

This PR makes it so that the existing secret is used instead of generating a new name.

Jira: https://issues.redhat.com/browse/CNV-37629

[openshift-ci-robot]

@pcbailey: This pull request references CNV-37629 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

When configuring an existing SSH secret for the namespace in which that secret resides in the "Manage SSH keys" section the UI displays the secret name with a randomly generated suffix. In actuality, that secret wasn't created and doesn't exist. This can be demonstrated by navigating away from that screen and returning to it. Upon doing so "Not configured" will be displayed for that namespace instead of the generated secret name.

This PR makes it so that the existing secret is used instead of generating a new name.

Jira: https://issues.redhat.com/browse/CNV-37629

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 APPROVED

This pull-request has been approved by: avivtur, pcbailey

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 [avivtur,pcbailey]

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

[gouyang]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@gouyang: new pull request created: #1756

In response to this:

/cherry-pick release-4.15

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.