Changing administration and maintenance of cluster, from current Bastion host (NPS Toolkit VM) to separate Bastion host

Continue to host the OC client on the existing NPS toolkit VM or choose to setup a separate virtual machine, which acts as the bastion host. The Bastion host consumes 1 vCPU and 2 GB of memory.

Use these steps to bring up a new bastion node outside of the NPS toolkit VM.

Prerequisites

Any latest Linux host or VM with 1 vCPU and 2 GB memory.
Ensure that DNS and Load Balancers are reachable from the Bastion host.

Procedure

Copy the oc client binary from the NPS Toolkit VM to the Bastion Host and untar openshift-client-linux-<version>.tar.gz.
Copy the ignition files from /var/nps/ISO of the NPS Toolkit VM to the bastion host.
Copy the id_rsa and id_rsa.pub from /var/nps/ISO to bastion host.
Run either of the following commands to access the OpenShift cluster:
- Log in to the CLI using the oc login command:
```
oc login -u kubeadmin -p <7NDep-cBeIn-P4vcE-D6jc8> --server=https://<api.ocp4.nfv.com:6443>
```
- Access the cluster as system admin user and run the following:
```
export KUBECONFIG=/var/nps/ISO/ign_config/auth/kubeconfig
```
- Access the OpenShift web-console at https://console-openshift-console.apps.<cluster_name>.<domain_name>.com.