Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-4736

OCP 4.21 - Console Dependencies & Tech Debt

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • openshift-4.20
    • None
    • None
    • OCP 4.21 - Console Dependencies & Tech Debt
    • Quality / Stability / Reliability
    • 62% To Do, 23% In Progress, 15% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Over time, our OpenShift Console has accumulated technical debt in its libraries, frameworks, and underlying infrastructure. This epic is focused on auditing, updating, and standardizing dependencies to the latest supported versions, while ensuring compatibility and minimizing user impact. Addressing this tech debt will:

      • Reduce security vulnerabilities by patching known CVEs
      • Improve performance through optimized libraries
      • Streamline developer onboarding and maintenance
      • Lay the groundwork for future features by aligning on current platform standards

      Goals & Objectives:

      1. Frontend Dependencies
        • Audit third-party UI components (React, PatternFly, etc.)
        • Upgrade to the latest stable major versions
        • Refactor any deprecated APIs
      1. Backend Dependencies
        • Update Go modules and middleware libraries
        • Migrate from deprecated frameworks (if applicable)
        • Ensure backward compatibility for REST/gRPC endpoints
      1. Infrastructure
        • Harden CI/CD pipelines with up-to-date build agents
        • Refresh container base images (e.g., Red Hat UBI versions)
        • Align Kubernetes manifests with current API versions

      Acceptance Criteria:

      • All frontend NPM package versions are updated to their latest non-breaking releases, with no failing unit or e2e tests.
      • Backend Go modules have no outdated major versions; existing integration tests pass without regression.
      • CI/CD pipeline definitions use current Docker image tags; all automated builds succeed in consumed staging clusters.
      • No known high- or critical-severity vulnerabilities remain in project dependencies (scan report attached).
      • Documentation updated to reflect new version requirements and rollback procedures.

              Unassigned Unassigned
              jhadvig@redhat.com Jakub Hadvig
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: