console
by
openshift

Description: OpenShift Cluster Console UI

View on GitHub ↗

Summary Information

Updated 21 minutes ago
Added to GitGenius on June 23rd, 2023
Created on April 13th, 2018
Open Issues & Pull Requests: 166 (+0)
Number of forks: 726
Total Stargazers: 457 (+0)
Total Subscribers: 103 (+0)

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 38 days
Stale 30+ days: 2
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 2

Top labels

  • lifecycle/rotten (93)
  • kind/bug (56)
  • triage/support (38)
  • component/olm (35)
  • kind/feature (34)
  • component/dev-console (14)
  • lifecycle/stale (14)
  • component/core (11)

Repository Insights (GitGenius)

Median issue/PR response: 18.4 days
Mean response time: 227.3 days
90th percentile: 685.9 days
Tracked items: 54

Most active contributors

Detailed Description

The OpenShift Console, codenamed Bridge, is a web-based user interface that serves as a more accessible alternative to kubectl for managing OpenShift and Kubernetes clusters. Written primarily in TypeScript, it functions as a single-page web application that provides cluster administration capabilities through a graphical interface. The console integrates with multiple backend services including monitoring systems, chargeback services, and the Operator Lifecycle Manager, while also handling critical infrastructure tasks like proxying the Kubernetes API, managing user authentication, and serving frontend static assets.

The repository is classified across multiple domains reflecting its comprehensive scope: management, dashboard, cloud-native user interface, developer tools, web console, cluster administration, DevOps tools, and application deployment. It serves as both a management interface and an extension point for OpenShift functionality, supporting customization and operator integration alongside standard resource monitoring and application management capabilities.

Development of the console requires Node.js version 22 or higher with corepack enabled for Yarn Berry, Go 1.25 or later, and either the oc or kubectl command-line tools connected to an OpenShift or Kubernetes cluster. The project uses Go modules and maintains separate frontend and backend codebases, with frontend code located in the frontend directory using Node, Yarn, and Webpack to compile dependencies into dynamically loaded bundles. The backend binaries are output to a bin directory after compilation.

The repository demonstrates active maintenance patterns tracked through GitGenius data, with a median issue and pull request response latency of 440.6 hours across 54 tracked items, though mean latency extends to 5454.4 hours indicating some longer-running discussions. The most active issue labels are lifecycle/rotten with 19 occurrences, followed by lifecycle/stale and lifecycle/frozen with 4 occurrences each. Primary contributors tracked by GitGenius include logonoff with 29 events, mikaello with 18 events, and spadgett with 13 events. The repository shares overlapping contributors with major projects including Microsoft's VSCode and TypeScript repositories as well as the Rust language project, indicating cross-pollination with significant open-source ecosystems.

The console supports multiple deployment and development scenarios including local development without authentication using kubeadmin tokens, authenticated development environments with OAuth client registration, and integration with CodeReady Containers for local cluster testing. For native Kubernetes environments, the application can run with kubectl-based configuration. The development workflow includes comprehensive testing infrastructure with unit tests for both backend and frontend components, interactive development mode with hot reloading capabilities, and Cypress-based integration testing with support for both headless and UI-based test execution.

The project includes detailed developer documentation covering dependency installation, interactive development workflows, debugging procedures, and test execution across multiple testing frameworks. The console operator in OpenShift 4.x handles installation and management of the console as a cluster component. The repository maintains contribution guidelines in a CONTRIBUTING file and enforces coding standards through a STYLEGUIDE document, establishing clear expectations for developers working on the codebase.

console
by
openshiftopenshift/console

Repository Details

Fetching additional details & charts...