Skip to content

README: Add console and cleanup information #402

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.

Sign up for GitHub

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

Merged
openshift-merge-robot merged 1 commit into from
Oct 4, 2018
Merged

README: Add console and cleanup information #402

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,3 +30,28 @@ hack/get-terraform.sh
```

The installer will show a series of prompts for user-specific information (e.g. admin password) and use reasonable defaults for everything else. In non-interactive contexts, prompts can be bypassed by providing appropriately-named environment variables. Refer to the [user documentation](docs/user) for more information.

### Connect to the cluster

#### Console

Shortly after the `cluster` command completes, the OpenShift console will come up at `https://${OPENSHIFT_INSTALL_CLUSTER_NAME}-api.${OPENSHIFT_INSTALL_BASE_DOMAIN}:6443/console/`.
You may need to ignore a certificate warning if you did not configure a certificate authority known to your browser.
Log in using the admin credentials you configured when creating the cluster.

#### Kubeconfig

You can also use the admin kubeconfig which `openshift-install cluster` placed under `--dir` (which defaults to `.`) in `auth/kubeconfig`.
If you launched the cluster with `openshift-install --dir "${DIR}" cluster`, you can use:

```sh
export KUBECONFIG="${DIR}/auth/kubeconfig"
```

### Cleanup

Destroy the cluster and release associated resources with:

```sh
openshift-install destroy-cluster
```
9 changes: 1 addition & 8 deletions docs/dev/libvirt-howto.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,16 +244,13 @@ ssh core@$MASTER_IP

### Inspect the cluster with kubectl

You'll need a `kubectl` binary on your path.
If you launched the cluster with `openshift-install --dir "${DIR}" cluster`, you can use:
You'll need a `kubectl` binary on your path and [the kubeconfig from your `cluster` call](../../README.md#kubeconfig).
Copy link
Contributor

@abhinavdahiya abhinavdahiya Oct 3, 2018

Choose a reason for hiding this comment

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

openshift usually recommends oc

Copy link
Member Author

@wking wking Oct 3, 2018

Choose a reason for hiding this comment

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

openshift usually recommends oc

Orthogonal change to existing code ;). File a follow-up PR?


```sh
export KUBECONFIG="${DIR}/auth/kubeconfig"
kubectl get -n tectonic-system pods
```

If you didn't set `--dir`, you can use `KUBECONFIG=auth/kubeconfig`.

Alternatively, you can run `kubectl` from the bootstrap or master nodes.
[SSH in](#ssh-access), and run:

Expand All @@ -262,10 +259,6 @@ export KUBECONFIG=/var/opt/tectonic/auth/kubeconfig
kubectl get --all-namespaces pods
```

### Connect to the cluster console

Visit `https://${OPENSHIFT_INSTALL_CLUSTER_NAME}-api.${OPENSHIFT_INSTALL_BASE_DOMAIN}:6443/console/` and log in using the admin credentials you configured when creating the cluster.

## FAQ

### Libvirt vs. AWS
Expand Down