NO-JIRA: Print the "export KUBECONFIG=..." command on its own line for easier cut-and-paste

[danwinship]

A long time ago I submitted a PR (#6018) to change the installer output from

INFO To access the cluster as the system:admin user when using 'oc',
run 'export KUBECONFIG=/path/to/installer/auth/kubeconfig'

to

INFO To access the cluster as the system:admin user when using 'oc', run
    export KUBECONFIG=/path/to/installer/auth/kubeconfig

for ease of cut-and-pasting, but then a few months later it accidentally got reverted due to a badly-resolved merge conflict in #5336.

This just puts it back to how it was in #6018 (which, FTR, is how README.md still claims it prints it).

[r4f4]

/lgtm

[sadasu]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu

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

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

[openshift-ci]

@danwinship: 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.

[openshift-ci-robot]

@danwinship: This pull request explicitly references no jira issue.

In response to this:

A long time ago I submitted a PR (#6018) to change the installer output from

INFO To access the cluster as the system:admin user when using 'oc',
run 'export KUBECONFIG=/path/to/installer/auth/kubeconfig'

to

INFO To access the cluster as the system:admin user when using 'oc', run
   export KUBECONFIG=/path/to/installer/auth/kubeconfig

for ease of cut-and-pasting, but then a few months later it accidentally got reverted due to a badly-resolved merge conflict in #5336.

This just puts it back to how it was in #6018 (which, FTR, is how README.md still claims it prints it).

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.