/overview

Name

node-team:overview

Synopsis

/node-team:overview [--sub-team core|devices|kueue]

Description

Displays a comprehensive overview of the OpenShift Node team: what the team owns, its responsibilities, component and repo mappings, sub-team structure, ceremonies, upstream community involvement, active sprints, and which specialized plugins handle which domain.

This is the entry point for understanding the Node team's scope and navigating to the right tool for a given task.

Implementation

1. Read shared references:

   • Team mission, responsibilities, ceremonies, Slack channels, customer support tools, key links, and plugin routing from shared/team-info.md
   • Component list and repo mappings from shared/components.md
   • Sub-team assignments from the sub-teams table in shared/components.md
   • Sprint and board info from jira.md
   • OCP-to-K8s version mapping from shared/version-map.md

2. If --sub-team is specified, filter the Component Ownership table and Sub-teams table to that sub-team's components. All other sections (ceremonies, Slack channels, upstream communities, key links, plugin routing) are always shown in full since they apply team-wide.

3. Present a structured summary with these sections from the references:

   • Team Mission and Responsibilities (from team-info.md)
   • Component Ownership table (from components.md)
   • Sub-teams table (from components.md). If roster files exist at ~/.node-assistant/team-roster-{core,dra,kueue}.json, include member count per sub-team.
   • Ceremonies and sprint cadence (from team-info.md)
   • Upstream Communities (from team-info.md)
   • Slack Channels and Mailing Lists (from team-info.md)
   • Customer Support Tools (from team-info.md)
   • Active Sprints (best-effort): query the Jira Agile API (board 11478) for active sprints per jira.md. List sprint names and dates. If the API call fails (missing credentials, network issues), print "Sprint data unavailable" and continue with the remaining sections.
   • Version Mapping: show the current OCP-to-K8s version mapping from shared/version-map.md for the latest 2-3 OCP releases.
   • Plugin Routing table (from team-info.md)
   • Key Links (from team-info.md)

Return Value

Formatted text summary of team mission, responsibilities, components, sub-teams, ceremonies, upstream communities, active sprints, version mapping, plugin routing, and key links.

Examples

1. Full team overview:

   /node-team:overview
   

2. DRA/Devices sub-team only:

   /node-team:overview --sub-team devices
   

3. Kueue sub-team only:

   /node-team:overview --sub-team kueue
   

Arguments

• --sub-team <name>: Filter to a specific sub-team (core, devices, or kueue). Optional; shows all components when omitted.