Skip to content

1.1. Introducing the Console and Signing In

When to Read This Chapter

Read this when you connect to the Console for the first time, or when you want to learn where things are on screen. Individual features are covered in their own chapters.

Kubernetes and the Console

Kubernetes is a system that groups several servers together to run and manage containers. When you declare "this is the state I want", Kubernetes keeps adjusting to maintain that state. If a pod terminates it starts a new one; if a node goes down it moves the workload to another node.

Every declaration and adjustment goes through the API server. The command-line tool (kubectl) and the Console call the same API. The Console is that API wrapped in a screen.

So what you do in the Console produces the same result as doing it from the command line, and changes made from the command line show up in the Console right away.

What You Can Do With the Console

AreaWhat you doChapter
Checking statusCluster resource usage, pod and node status, events2.1
Managing workloadsViewing and editing pods, Deployments, and Jobs; logs; web terminal3.1
Building and deployingBuilding images from source (S2I), installing Helm charts4.2, 9.1
Networking and storageConfiguring Services and Ingresses, checking volume claims5.1, 6.1
SecuritySetting access permissions, managing user groups, checking certificates7.1

Connecting and Signing In

Open the Console address in a browser. Ask your installation staff for the address.

Console sign-in screen

Opening any address while signed out brings you to this screen. After you sign in, you continue to the screen you originally requested.

You can change the display language in the language selector at the bottom left of the screen.

Two Authentication Methods

ButtonDescriptionWhen to use it
Sign In with SSOGoes to the integrated authentication server and signs in with your accountThis is the usual method
Use A TokenPastes a service account token directlyTemporary checks, automation accounts

Selecting Sign In with SSO opens a new authentication window. Enter your account and password, and once you sign in the window closes and you enter the Console.

Kubernetes itself has no resource called a "user". Users are managed by an external authentication server, and Kubernetes receives only the user name and groups carried in the authentication result to decide permissions. So creating and removing accounts is done on the authentication server, not in the Console (see 7.2).

Screen Layout

After signing in, the overview screen appears.

Console overview screen

The screen has three areas.

AreaPositionContents
Top barTop of the screenProduct logo, global search, display settings, account menu
Left menuLeft sideFeature categories
Main areaCenterThe list or detail for the selected menu

Left Menu Structure

Menus are grouped by the nature of the resource.

MenuWhat it holdsChapter
ClusterNamespaces, Nodes, Certificates, CIS Benchmark, Cluster Diagnostics2.1
MapResource relationship diagram2.2
WorkloadsPods and the controllers that manage them3.1
BuildBuild configurations and build history4.2
NetworkServices, Ingresses, network policies5.1
StorageVolume claims and the actual storage6.1
DevicesSpecial devices such as GPUs8.3
SecurityService accounts, roles, role bindings7.1
User ManagementPermissions for users and groups7.2
ConfigurationResource limits, priorities, webhooks8.1
Custom ResourcesResources added by extensions8.2
Cert-managercert-manager certificates7.3
Helm ChartsReleases and repositories9.1
ToolsLinks to external systems9.3
SettingsDisplay settings9.4

The Create button below the menu lets you create a resource by entering YAML directly. The product version and build time appear at the very bottom.

Top Bar

ElementRole
Product logoReturns to the overview screen
Search boxFinds resources by name regardless of resource type
List-shaped iconCollapses and expands the left menu
Moon or sun shapeSwitches between the light and dark screen
Square shapeSwitches to full screen
Person shapeAccount information and sign-out

Global search can be focused directly with Ctrl + / (⌘ + / on macOS). It is useful when you do not know which menu a resource is under.

The Console hides menus for resources you cannot view. So the menu layout can differ from person to person.

If a menu mentioned in this document is not on your screen, you do not have permission to view that resource. Ask your operations staff for permission if you need it (see 7.2).