Appendix: SNO Cluster Access Information

Overview

This appendix provides comprehensive access information for your Single Node OpenShift (SNO) cluster, including SSH connection details, node information, console access, and credentials.

Quick Reference

Item Value

Bastion SSH Host

bastion.student1.sandbox5466.opentlc.com

Bastion Username

lab-user

Bastion Password

Provided by workshop administrator

Console URL

https://console-openshift-console.apps.ocp.student1.sandbox5466.opentlc.com

API URL

https://api.ocp.student1.sandbox5466.opentlc.com:6443

kubeadmin Username

kubeadmin

kubeadmin Password

Run: cat ~/kubeadmin-password

SSH Access Information

Bastion Host Connection

The bastion host provides SSH access to your SNO cluster environment. The bastion has oc, kubectl, and KUBECONFIG pre-configured.

SSH Host

bastion.student1.sandbox5466.opentlc.com

Username

lab-user

Password

Provided by workshop administrator

  1. Connect to your bastion host:

    ssh lab-user@bastion.student1.sandbox5466.opentlc.com

    Enter the password when prompted: Provided by workshop administrator

Once connected to the bastion, you can immediately run cluster commands - no additional login required. The bastion is pre-authenticated as system:admin.

Verify Connection

After connecting to the bastion:

# Verify cluster access (already authenticated as system:admin)
oc whoami
oc get nodes

Expected output: * User: system:admin * One node in Ready state with roles control-plane,master,worker

SNO Node Information

Getting Node Name

The SNO cluster has a single node that serves as both control plane and worker.

  1. Get the SNO node name:

    # From the bastion (already authenticated)
oc get nodes

# Or get just the node name
oc get nodes -o jsonpath='{.items[0].metadata.name}'

    Expected output: A single node with roles control-plane,master,worker

Node Details

  1. Get detailed node information:

    # Get the node name first
TARGET_NODE=$(oc get nodes -o jsonpath='{.items[0].metadata.name}')
echo "Target node: $TARGET_NODE"

# Get comprehensive node information
oc describe node $TARGET_NODE

# Get node roles and labels
oc get node $TARGET_NODE --show-labels

# Get node IP addresses
oc get node $TARGET_NODE -o jsonpath='{.status.addresses[*].address}'

Node Resource Information

  1. Get CPU and memory information:

    # Load node name
TARGET_NODE=$(oc get nodes -o jsonpath='{.items[0].metadata.name}')

# Get CPU topology
oc debug node/$TARGET_NODE -- chroot /host lscpu | grep -E "(CPU\(s\)|Thread|Core|Socket|NUMA)"

# Get memory information
oc debug node/$TARGET_NODE -- chroot /host free -h

# Get node capacity and allocatable resources
oc describe node $TARGET_NODE | grep -E "(Capacity:|Allocatable:)" -A 10

Node Status

  1. Check node health and status:

    # Get node status
oc get nodes -o wide

# Get node conditions
oc get node $(oc get nodes -o jsonpath='{.items[0].metadata.name}') \
    -o jsonpath='{.status.conditions[*].type}{"\n"}{.status.conditions[*].status}'

# Check for any node issues
oc get events --field-selector involvedObject.kind=Node --sort-by='.lastTimestamp' | tail -10

Console and API Access

Console URL

The OpenShift web console provides a graphical interface for managing your cluster.

Your Console URL: https://console-openshift-console.apps.ocp.student1.sandbox5466.opentlc.com

  1. Access the console:

Browser Certificate Warning

You may see a certificate warning when first accessing the console. This is normal for self-signed certificates. Click "Advanced" and "Proceed to site" to continue.

API URL

The OpenShift API endpoint is used by the oc CLI and other tools.

Your API URL: https://api.ocp.student1.sandbox5466.opentlc.com:6443

  1. Use the API URL with oc CLI:

    # Login using API URL (from outside the bastion)
oc login https://api.ocp.student1.sandbox5466.opentlc.com:6443 \
    -u kubeadmin \
    -p 

# Verify connection
oc whoami
oc get nodes

Credentials

kubeadmin Username

The default administrator username for OpenShift is kubeadmin.

Username: kubeadmin

This is the standard username for initial cluster access and does not change.

kubeadmin Password

The kubeadmin password is unique for each cluster deployment.

Password Location: Run: cat ~/kubeadmin-password

  1. Retrieve the kubeadmin password from the bastion:

    # On the bastion (as lab-user), read the kubeadmin password
sudo cat /home/ec2-user/ocp/auth/kubeadmin-password

Password Security

The kubeadmin password provides full cluster administrator access. Keep it secure and do not share it publicly. After initial setup, consider creating additional users with appropriate roles.

CLI Login Instructions

  1. Login to the cluster using oc CLI (from bastion - already authenticated):

    # On the bastion, you're already authenticated as system:admin
oc whoami

# If you need to login as kubeadmin instead:
oc login {openshift_api_url} \
    -u kubeadmin \
    -p $(sudo cat /home/ec2-user/ocp/auth/kubeadmin-password)

  2. Login from outside the bastion:

    # Interactive login (will prompt for password)
oc login https://api.ocp.student1.sandbox5466.opentlc.com:6443 -u kubeadmin
# Enter password when prompted

# Or with password directly
oc login https://api.ocp.student1.sandbox5466.opentlc.com:6443 \
    -u kubeadmin \
    -p

  3. Verify authentication:

    # Check current user
oc whoami

# Check API server
oc whoami --show-server

# Verify cluster access
oc get nodes
oc get namespaces

Web Console Login

  1. Access the web console:

    1. Open your web browser

    2. Navigate to: https://console-openshift-console.apps.ocp.student1.sandbox5466.opentlc.com

    3. Select "kubeadmin" as the authentication method

    4. Enter username: kubeadmin

    5. Enter password: (from sudo cat /home/ec2-user/ocp/auth/kubeadmin-password on bastion)

    6. Click "Log In"

First Login

On first login, you may be prompted to change the kubeadmin password. This is optional but recommended for security.

Common Commands

  1. Quick access commands (run from bastion):

    # Get node name
oc get nodes -o jsonpath='{.items[0].metadata.name}'

# Get kubeadmin password
sudo cat /home/ec2-user/ocp/auth/kubeadmin-password

# Check cluster status
oc get clusterversion
oc get nodes
oc get co  # cluster operators

  2. SSH to bastion (from your local machine):

    ssh lab-user@bastion.student1.sandbox5466.opentlc.com
# Password: Provided by workshop administrator

Troubleshooting Access Issues

Cannot Connect to Bastion

  1. Troubleshooting steps:

    # Verify bastion hostname is correct
ping -c 3 bastion.student1.sandbox5466.opentlc.com

# Check SSH connectivity with verbose output
ssh -v lab-user@bastion.student1.sandbox5466.opentlc.com

# Verify you're using the correct password
# Password: Provided by workshop administrator

Cannot Access Console

  1. Troubleshooting steps:

    # Verify console URL is correct
curl -k -I https://console-openshift-console.apps.ocp.student1.sandbox5466.opentlc.com

# Get the kubeadmin password from bastion
ssh lab-user@bastion.student1.sandbox5466.opentlc.com "sudo cat /home/ec2-user/ocp/auth/kubeadmin-password"

Cannot Login with oc CLI

  1. Troubleshooting steps:

    # Verify API URL is accessible
curl -k https://api.ocp.student1.sandbox5466.opentlc.com:6443

# Try interactive login to see error messages
oc login https://api.ocp.student1.sandbox5466.opentlc.com:6443 -u kubeadmin

# From bastion, verify cluster is accessible
ssh lab-user@bastion.student1.sandbox5466.opentlc.com "oc get nodes"

Getting Help

If you continue to experience access issues, contact your workshop administrator with: * Your username: student1 * The specific error message * Output from the troubleshooting commands above

Summary

Access Type Details

SSH to Bastion

ssh lab-user@bastion.student1.sandbox5466.opentlc.com
Password: Provided by workshop administrator

Web Console

URL: https://console-openshift-console.apps.ocp.student1.sandbox5466.opentlc.com
Username: kubeadmin
Password: Run sudo cat /home/ec2-user/ocp/auth/kubeadmin-password on bastion

API Access

URL: https://api.ocp.student1.sandbox5466.opentlc.com:6443
Login: oc login https://api.ocp.student1.sandbox5466.opentlc.com:6443 -u kubeadmin

Pre-configured Access

On bastion, oc commands work immediately (authenticated as system:admin)

Best Practice

The easiest workflow is to SSH to the bastion and run all oc commands from there. The bastion is pre-configured with cluster access, so you don’t need to worry about authentication or kubeconfig files.