Skip to Content
Deploying ApplicationsApplication dashboard

Application dashboard

Use the application dashboard to check an application’s delivery status, deployed versions, runtime health, and ingress URLs without leaving the Core Platform UI.

Sign in and select a tenant

Choose Sign in with Core Platform to authenticate through Core Platform Auth. Your organisation may use a Google account brokered by Core Platform Auth or an approved local account.

Use the tenant selector in the dashboard header to change between supported tenants. Each tenant has isolated users, GitHub connections, catalogues, connected clusters, and runtime state. Available capabilities depend on the selected tenant; for example, some tenants provide a Git-backed catalogue and others provide connected-cluster onboarding.

Choose Log out to clear the Portal session. The Portal also attempts to end the associated Core Platform Auth session and displays a warning if Core Platform Auth cannot confirm logout. Sessions created before the Keycloak cutover are not retained.

Your GitHub connection is separate from Portal sign-in and belongs to the active Portal tenant. Open your profile and connect GitHub in each tenant where you need to perform operations using your GitHub identity.

Check delivery status

Open the dashboard and go to Applications, then choose the application. The Path to Production tab shows the current version in each stage, the status of build and test jobs, and links back to the underlying delivery evidence.

Application Path to Production status in the dashboard

Use this view when you need to answer questions such as:

  • which version is in fast feedback, extended test, or production
  • whether build, functional, non-functional, integration, extended test, or production deployment has passed
  • where to find the related GitHub workflow, logs, or deployment evidence

Check runtime health and ingress URLs

Select the Runtime tab to see replicas, pod CPU, pod memory, and the ingresses created for the application across environments.

Application runtime ingresses in the dashboard

The ingress table shows the environment, namespace, host, and backend for each application ingress. Use the external-link icon beside a host to open the endpoint.

CLI alternatives

Use corectl and kubectl when you need terminal access to the same runtime information:

corectl env connect <env-name>
kubectl get pods --namespace <namespace>
kubectl get ingress --namespace <namespace>

For delivery workflow details, see Path To Production.

Application MonitoringExpose your service via Ingress