Skip to content
Docs  >  Getting Started  >  Learn the Basics  >  Navigate OpenShift Console

Navigate OpenShift Console

Learn how to navigate the OpenShift web console to view and manage your deployed applications effectively.

Introduction

The OpenShift web console provides administrators and developers with tools to manage clusters, applications, and resources. Use the console to deploy applications, monitor performance, and troubleshoot issues.

Accessing the Console

Login Process

  1. Find the Console URL by navigating to developers.intility.com/clusters and selecting your cluster

  2. Click "Connect to your cluster" - you'll be automatically logged in via SSO

Bookmark Your Console

Save the console URL to your bookmarks for quick access. Each cluster has its own unique console URL.

Common Tasks

Finding Your Applications

  1. Select your project using the project dropdown
  2. Navigate to Workloads > Deployments to see running applications
  3. Check Routes in Networking > Routes for public URLs

Viewing Application Logs

# Multiple ways to access logs:

Via Console:

  1. Workloads > Pods → Select pod → Logs tab
  2. Workloads > Deployments → Select deployment → Pods tab → Select pod

CLI Equivalent: 

oc logs deployment/my-app
oc logs -f pod/my-app-pod  # Follow logs in real-time

Checking Application Health

  1. Deployment Status - Green indicates healthy, red indicates issues
  2. Pod Status - Running/Ready count should match desired replicas
  3. Events - Check for recent warning or error events
  4. Metrics - Monitor CPU, memory, and network usage

Accessing Applications

  1. Find the Route in Networking > Routes
  2. Click the Location URL to open your application
  3. Verify SSL certificate (look for the lock icon)

Scaling Applications

Via Console:

  1. Navigate to Workloads > Deployments
  2. Click on your deployment
  3. Click Actions > Edit Deployment
  4. Modify the replicas field

Via CLI: 

oc scale deployment/my-app --replicas=3

Troubleshooting Common Issues

Application Not Loading

  1. Check Route Status - Ensure route exists and is properly configured
  2. Verify Service - Confirm service is selecting the correct pods
  3. Pod Health - Ensure pods are running and ready
  4. Check Logs - Look for application startup errors

Pod Issues

Pod Stuck in Pending: - Check resource requests vs. cluster capacity - Verify node selectors and affinity rules - Review persistent volume claims

Pod Crashing: - Check application logs for errors - Verify resource limits aren't too restrictive - Review health check configurations

Performance Issues

  1. Resource Usage - Monitor CPU and memory consumption
  2. Network Latency - Check service mesh and ingress configuration
  3. Storage Performance - Verify persistent volume performance

Next Steps

Continue learning the basics:

Ready for advanced topics: