Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #705 Document remote set up, client connection #1473

Merged
merged 1 commit into from
Aug 21, 2020

Conversation

kowen-rh
Copy link
Contributor

This is based on the work of Trevor McKay published as a Gist: https://gist.github.com/tmckayus/8e843f90c44ac841d0673434c7de0c6a

Thank you for the assistance, @tmckayus!

Fixes: Issue #705

@cfergeau
Copy link
Contributor

Should we strongly advise to only do this on a local network, and that the remote server should not be exposed on the internet unless the user really understands the implications of this?


* {prod} is installed and set up on the remote server.
For more information, see link:{crc-gsg-url}#installing-codeready-containers_gsg[Installing {prod}] and link:{crc-gsg-url}#setting-up-codeready-containers_gsg[Setting up {prod}].
* Your user account has `sudo` permissions on the remote server.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sudo permissions is already part of #setting-up-codeready-containers_gsg, I don't know if it needs to be mentioned again?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True. I included this as a prerequisite here to make it clear that sudo (or root access in general) will be required for the commands included in this procedure. I'm not sure that the duplication needs to be changed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, fine with me!

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfergeau, robin-owen

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:

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

@openshift-ci-robot
Copy link

@robin-owen: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-crc 96505a8 link /test e2e-crc

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/test-infra repository. I understand the commands that are listed here.

@praveenkumar praveenkumar merged commit d402b05 into crc-org:master Aug 21, 2020
@tmckayus
Copy link
Contributor

This is based on the work of Trevor McKay published as a Gist: https://gist.github.com/tmckayus/8e843f90c44ac841d0673434c7de0c6a

Thank you for the assistance, @tmckayus!

Fixes: Issue #705

you are so welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants