Hide Forgot
1. Proposed title of this feature request =>unable to SCP to LTM when using F5 integration, require additional option in F5 LTM router deployment 3. What is the nature and description of the request? => Our LTM environment is using remote user accounts, as a result we're unable to use the user which we've given access to the LTM via TACAS as the account to SCP PEM certificates to because as per : https://support.f5.com/kb/en-us/solutions/public/13000/400/sol13454.html#remoteclient it's not possible to do this. We need to configure the F5 LTM to use a different user account to SCP, than that it uses to interact with the LTM API, please create a patch to allow this, as you can see in https://github.com/openshift/origin/blob/master/pkg/router/f5/f5.go sshUserHost builds up the ssh command using f5.username which is the same username used for the web API. We'd like the option to specify SCP User seperately.
This bug has been identified as a dated (created more than 3 months ago) bug. This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, as it is currently not part of the products immediate priorities. Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.