Bug 1956414 - [DOC] Remove mention of multiple ssh-keys from user doc as it is currently not officially supported
Summary: [DOC] Remove mention of multiple ssh-keys from user doc as it is currently no...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Rolfe Dlugy-Hegwer
QA Contact: To Hung Sze
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 16:09 UTC by To Hung Sze
Modified: 2021-05-07 15:58 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-07 15:58:08 UTC
oVirt Team: Docs
Target Upstream Version:


Attachments (Terms of Use)

Description To Hung Sze 2021-05-03 16:09:28 UTC
Document URL: 
https://docs.openshift.com/container-platform/4.7/installing/installing_aws/installing-aws-customizations.html#installation-configuration-parameters_installing-aws-customizations

Section Number and Name: 
Installation configuration parameters
Table 2. Optional parameters
One or more keys. For example:


sshKey:
  <key1>
  <key2>
  <key3>

Describe the issue: 
Multiple ssh-keys is not officially supported (but possible).

Suggestions for improvement: 
Until engineering team supports multiple ssh-keys properly, remove mentioning of multiple ssh-keys from user facing doc.

Additional information: 
Multiple ssh-keys is introduced via:
https://github.com/openshift/openshift-docs/pull/22718#discussion_r479990090

Also mentioned in support doc:
https://access.redhat.com/solutions/5638721 (marked as SOLUTION UNVERIFIED)

A Jira ticket would be required if there is a need to support multiple ssh-keys at install time.

This should be applicable to all platforms.

Comment 1 Rolfe Dlugy-Hegwer 2021-05-07 15:58:08 UTC
https://github.com/openshift/openshift-docs/pull/32138


Note You need to log in before you can comment on or make changes to this bug.