OSD-27572: Require a reason for using osdctl cluster ssh key

[joshbranham]

I used this command and received a compliance ticket to fill out. This just plumbs one through via osdctl cluster ssh key --elevation-reason $reason. I made this flag required as well so you don't do the harder thing by default.

I am going to update all the SOPs as well that don't reference this command to do so once this is released. Will link that PR here.

> ./osdctl cluster ssh key --elevation-reason "#ITN-2024-00286" -S
Cluster:
	Name:	trbo-prod-cp-10
	ID:	2f785ugk0tgdjfovqkmc65dr1jn2d0st
	UUID:	0a1051d5-fb5f-44bd-8855-134fa08eace1

Continue? (y/N): y

INFO[0006] Backplane URL retrieved via OCM environment: https://api.backplane.openshift.com
INFO[0007] No PagerDuty API Key configuration available. This will result in failure of `ocm-backplane login --pd <incident-id>` command.
INFO[0009] Backplane URL retrieved via OCM environment: https://api.backplane.openshift.com
INFO[0009] No PagerDuty API Key configuration available. This will result in failure of `ocm-backplane login --pd <incident-id>` command.
-----BEGIN RSA PRIVATE KEY-----
.....

[tnierman]

/lgtm

[openshift-ci-robot]

@joshbranham: This pull request references OSD-27572 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.19.0" version, but no target version was set.

In response to this:

I used this command and received a compliance ticket to fill out. This just plumbs one through via osdctl cluster ssh key --elevation-reason $reason. I made this flag required as well so you don't do the harder thing by default.

I am going to update all the SOPs as well that don't reference this command to do so once this is released. Will link that PR here.

> ./osdctl cluster ssh key --elevation-reason "#ITN-2024-00286" -S
Cluster:
  Name:	trbo-prod-cp-10
  ID:	2f785ugk0tgdjfovqkmc65dr1jn2d0st
  UUID:	0a1051d5-fb5f-44bd-8855-134fa08eace1

Continue? (y/N): y

INFO[0006] Backplane URL retrieved via OCM environment: https://api.backplane.openshift.com
INFO[0007] No PagerDuty API Key configuration available. This will result in failure of `ocm-backplane login --pd <incident-id>` command.
INFO[0009] Backplane URL retrieved via OCM environment: https://api.backplane.openshift.com
INFO[0009] No PagerDuty API Key configuration available. This will result in failure of `ocm-backplane login --pd <incident-id>` command.
-----BEGIN RSA PRIVATE KEY-----
.....

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]

@joshbranham: all tests passed!

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.

[typeid]

/lgtm
/approve

Thanks Josh!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joshbranham, tnierman, typeid

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

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