Generate and analyze OpenShift node tuning profiles

version
1.0.1
GitHub stars
123

Install

/plugin install node-tuning@ai-helpers

Run it inside Claude Code after adding the marketplace with /plugin marketplace add openshift-eng/ai-helpers.

Contents

Discovered from source

Skills 1

Node Tuning Helper Scripts

Detailed instructions for invoking the helper utilities that back /node-tuning commands:

  • generate_tuned_profile.py renders Tuned manifests (tuned.openshift.io/v1).
  • analyze_node_tuning.py inspects live nodes or sosreports for tuning gaps.

When to Use These Scripts

  • Translate structured command inputs into Tuned manifests for the Node Tuning Operator.
  • Iterate on generated YAML outside the assistant or integrate the generator into automation.
  • Analyze CPU isolation, IRQ affinity, huge pages, sysctl values, and networking counters from live clusters or archived sosreports.

Prerequisites

  • Python 3.8 or newer (python3 --version).
  • Repository checkout so the scripts under plugins/node-tuning/skills/scripts/ are accessible.
  • Optional: oc CLI when validating or applying manifests.
  • Optional: Extracted sosreport directory when running the analysis script offline.
  • Optional (remote analysis): oc CLI access plus a valid KUBECONFIG when capturing /proc//sys or sosreport via oc debug node/<name>. The sosreport workflow pulls the registry.redhat.io/rhel9/support-tools image (override with --toolbox-image or TOOLBOX_IMAGE) and requires registry access. HTTP(S) proxy env vars from the host are forwarded automatically when present, but using a proxy is optional.

Script: generate_tuned_profile.py

Implementation Steps

  1. Collect Inputs

    • --profile-name: Tuned resource name.
    • --summary: [main] section summary.
    • Repeatable options: --include, --main-option, --variable, --sysctl, --section (SECTION:KEY=VALUE).
    • Target selectors: --machine-config-label key=value, --match-label key[=value].
    • Optional: --priority (default 20), --namespace, --output, --dry-run.
    • Use --list-nodes/--node-selector to inspect nodes and --label-node NODE:KEY[=VALUE] (plus --overwrite-labels) to tag machines.
  2. Inspect or Label Nodes (optional)

    # List all worker nodes
    python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py --list-nodes --node-selector "node-role.kubernetes.io/worker" --skip-manifest
    
    # Label a specific node for the worker-hp pool
    python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
      --label-node ip-10-0-1-23.ec2.internal:node-role.kubernetes.io/worker-hp= \
      --overwrite-labels \
      --skip-manifest
    
  3. Render the Manifest

    python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
      --profile-name "$PROFILE" \
      --summary "$SUMMARY" \
      --sysctl net.core.netdev_max_backlog=16384 \
      --match-label tuned.openshift.io/custom-net \
      --output .work/node-tuning/$PROFILE/tuned.yaml
    
    • Omit --output to write <profile-name>.yaml in the current directory.
    • Add --dry-run to print the manifest to stdout.
  4. Review Output

    • Inspect the generated YAML for accuracy.
    • Optionally format with yq or open in an editor for readability.
  5. Validate and Apply

    • Dry-run: oc apply --server-dry-run=client -f <manifest>.
    • Apply: oc apply -f <manifest>.

Error Handling

  • Missing required options raise ValueError with descriptive messages.
  • The script exits non-zero when no target selectors (--machine-config-label or --match-label) are supplied.
  • Invalid key/value or section inputs identify the failing argument explicitly.

Examples

python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
  --profile-name realtime-worker \
  --summary "Realtime tuned profile" \
  --include openshift-node --include realtime \
  --variable isolated_cores=1 \
  --section bootloader:cmdline_ocp_realtime=+systemd.cpu_affinity=${not_isolated_cores_expanded} \
  --machine-config-label machineconfiguration.openshift.io/role=worker-rt \
  --priority 25 \
  --output .work/node-tuning/realtime-worker/tuned.yaml
python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
  --profile-name openshift-node-hugepages \
  --summary "Boot time configuration for hugepages" \
  --include openshift-node \
  --section bootloader:cmdline_openshift_node_hugepages="hugepagesz=2M hugepages=50" \
  --machine-config-label machineconfiguration.openshift.io/role=worker-hp \
  --priority 30 \
  --output .work/node-tuning/openshift-node-hugepages/hugepages-tuned-boottime.yaml

Script: analyze_node_tuning.py

Purpose

Inspect either a live node (/proc, /sys) or an extracted sosreport snapshot for tuning signals (CPU isolation, IRQ affinity, huge pages, sysctl state, networking counters) and emit actionable recommendations.

Usage Patterns

  • Live node analysis
    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py --format markdown
    
  • Remote analysis via oc debug
    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py \
      --node worker-rt-0 \
      --kubeconfig ~/.kube/prod \
      --format markdown
    
  • Collect sosreport via oc debug and analyze locally
    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py \
      --node worker-rt-0 \
      --toolbox-image registry.example.com/support-tools:latest \
      --sosreport-arg "--case-id=01234567" \
      --sosreport-output .work/node-tuning/sosreports \
      --format json
    
  • Offline sosreport analysis
    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py \
      --sosreport /path/to/sosreport-2025-10-20
    
  • Automation-friendly JSON
    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py \
      --sosreport /path/to/sosreport \
      --format json --output .work/node-tuning/node-analysis.json
    

Implementation Steps

  1. Select data source
    • Provide --node <name> (with optional --kubeconfig / --oc-binary). By default the helper runs sosreport remotely from inside the RHCOS toolbox container (registry.redhat.io/rhel9/support-tools). Override the image with --toolbox-image, extend the sosreport command with --sosreport-arg, or disable the curated OpenShift flags via --skip-default-sosreport-flags. Pass --no-collect-sosreport to fall back to the direct /proc snapshot mode.
    • Provide --sosreport <dir> for archived diagnostics; detection finds embedded proc/ and sys/.
    • Omit both switches to query the live filesystem (defaults to /proc and /sys).
    • Override paths with --proc-root or --sys-root when the layout differs.
  2. Run analysis
    • The script parses cpuinfo, kernel cmdline parameters (isolcpus, nohz_full, tuned.non_isolcpus), default IRQ affinities, huge page counters, sysctl values (net, vm, kernel), transparent hugepage settings, netstat/sockstat counters, and ps snapshots (when available in sosreport).
  3. Review the report
    • Markdown output groups findings by section (System Overview, CPU & Isolation, Huge Pages, Sysctl Highlights, Network Signals, IRQ Affinity, Process Snapshot) and lists recommendations.
    • JSON output contains the same information in structured form for pipelines or dashboards.
  4. Act on recommendations
    • Apply Tuned profiles, MachineConfig updates, or manual sysctl/irqbalance adjustments.
    • Feed actionable items back into /node-tuning:generate-tuned-profile to codify desired state.

Error Handling

  • Missing proc/ or sys/ directories trigger descriptive errors.
  • Unreadable files are skipped without raising an error and noted in observations where relevant.
  • Non-numeric sysctl values are flagged for manual investigation.

Example Output (Markdown excerpt)

# Node Tuning Analysis

## System Overview
- Hostname: worker-rt-1
- Kernel: 4.18.0-477.el8
- NUMA nodes: 2
- Kernel cmdline: `BOOT_IMAGE=... isolcpus=2-15 tuned.non_isolcpus=0-1`

## CPU & Isolation
- Logical CPUs: 32
- Physical cores: 16 across 2 socket(s)
- SMT detected: yes
- Isolated CPUs: 2-15
...

## Recommended Actions
- Configure net.core.netdev_max_backlog (>=32768) to accommodate bursty NIC traffic.
- Transparent Hugepages are not disabled (`[never]` not selected). Consider setting to `never` for latency-sensitive workloads.
- 4 IRQs overlap isolated CPUs. Relocate interrupt affinities using tuned profiles or irqbalance.

Follow-up Automation Ideas

  • Persist JSON results in .work/node-tuning/<host>/analysis.json for historical tracing.
  • Gate upgrades by comparing recommendations across nodes.
  • Integrate with CI jobs that validate cluster tuning post-change.

Commands 2

Name

node-tuning:analyze-node-tuning

Synopsis

/node-tuning:analyze-node-tuning [--sosreport PATH] [--collect-sosreport|--no-collect-sosreport] [--sosreport-output PATH] [--node NODE] [--kubeconfig PATH] [--oc-binary PATH] [--format json|markdown] [--max-irq-samples N] [--keep-snapshot]

Description

The node-tuning:analyze-node-tuning command inspects kernel tuning signals gathered from either a live OpenShift node (/proc, /sys), an oc debug node/<name> snapshot captured via KUBECONFIG, or an extracted sosreport directory. It parses CPU isolation parameters, IRQ affinity, huge page allocation, critical sysctl settings, and networking counters before compiling actionable recommendations that can be enforced through Tuned profiles or MachineConfig updates.

Use this command when you need to:

  • Audit a node for tuning regressions after upgrades or configuration changes.
  • Translate findings into remediation steps for the Node Tuning Operator.
  • Produce JSON or Markdown reports suitable for incident response, CI gates, or documentation.

Implementation

  1. Establish data source

    • Live (local) analysis: the helper script defaults to /proc and /sys. Ensure the command runs on the target node (or within an SSH session / debug pod).
    • Remote analysis via oc debug: provide --node <name> (plus optional --kubeconfig and --oc-binary). The helper defaults to entering the RHCOS toolbox (backed by the registry.redhat.io/rhel9/support-tools image) via oc debug node/<name>, running sosreport --batch --quiet -e openshift -e openshift_ovn -e openvswitch -e podman -e crio -k crio.all=on -k crio.logs=on -k podman.all=on -k podman.logs=on -k networking.ethtool-namespaces=off --all-logs --plugin-timeout=600, streaming the archive locally (respecting --sosreport-output when set), and analyzing the extracted data. Use --toolbox-image (or TOOLBOX_IMAGE) to point at a mirrored support-tools image, --sosreport-arg to append extra flags (repeat per flag), or --skip-default-sosreport-flags to take full control. Host HTTP(S) proxy variables are forwarded when present but entirely optional. Add --no-collect-sosreport to skip sosreport generation entirely, and --keep-snapshot if you want to retain the downloaded files.
    • Offline analysis: provide --sosreport /path/to/sosreport-<timestamp> pointing to an extracted sosreport directory; the script auto-discovers embedded proc/ and sys/ trees.
    • Override non-standard layouts with --proc-root or --sys-root when auto-detection fails to locate the correct proc/ or sys/ trees.
  2. Prepare workspace

    • Create .work/node-tuning/<hostname>/ to store generated reports (remote snapshots and sosreport captures may reuse this path or default to a temporary directory).
    • Decide whether you want Markdown (human-readable) or JSON (automation-ready) output. Set --format json and --output for machine consumption.
  3. Invoke the analysis helper

    python3 plugins/node-tuning/skills/scripts/analyze_node_tuning.py \
      --sosreport "$SOS_DIR" \
      --format markdown \
      --max-irq-samples 10 \
      --output ".work/node-tuning/${HOSTNAME}/analysis.md"
    
    • Omit --sosreport and --node to evaluate the local environment.
    • Lower --max-irq-samples to cap the number of IRQ affinity overlaps listed in the report.
  4. Interpret results

    • System Overview: Validates kernel release, NUMA nodes, and kernel cmdline flags (isolcpus, nohz_full, tuned.non_isolcpus).
    • CPU & Isolation: Highlights SMT detection, isolated CPU masks, and mismatches between default IRQ affinity and isolated cores.
    • Huge Pages: Summarizes global and per-NUMA huge page pools, reserved counts, and sysctl targets.
    • Sysctl Highlights: Surfaces values for tuning-critical keys (e.g., net.core.netdev_max_backlog, vm.swappiness, THP state) with recommendations when thresholds are missed.
    • Network Signals: Examines TcpExt counters and sockstat data for backlog drops, syncookie failures, or orphaned sockets.
    • IRQ Affinity: Lists IRQs overlapping isolated CPUs so you can adjust tuned profiles or irqbalance policies.
    • Process Snapshot: When available in sosreport snapshots, shows top CPU consumers and flags irqbalance presence.
  5. Apply remediation

    • Feed the recommendations into /node-tuning:generate-tuned-profile or MachineConfig workflows.
    • For immediate live tuning, adjust sysctls or interrupt affinities manually, then rerun the analysis to confirm remediation.

Return Value

  • Success: Returns a Markdown or JSON report summarizing findings and recommended actions.
  • Failure: Reports descriptive errors (e.g., missing proc/ or sys/ directories, unreadable sosreport path) and exits non-zero.

Examples

  1. Analyze a live node and print Markdown

    /node-tuning:analyze-node-tuning --format markdown
    
  2. Capture /proc and /sys via oc debug (sosreport by default) and analyze remotely

    /node-tuning:analyze-node-tuning \
      --node worker-rt-0 \
      --kubeconfig ~/.kube/prod \
      --format markdown
    
  3. Collect a sosreport via oc debug (custom image + flags) and analyze it locally

    /node-tuning:analyze-node-tuning \
      --node worker-rt-0 \
      --toolbox-image registry.example.com/support-tools:latest \
      --sosreport-arg "--case-id=01234567" \
      --sosreport-output .work/node-tuning/sosreports \
      --format json
    
  4. Inspect an extracted sosreport and save JSON to disk

    /node-tuning:analyze-node-tuning \
      --sosreport ~/Downloads/sosreport-worker-001 \
      --format json \
      --max-irq-samples 20
    
  5. Limit the recommendation set to a handful of IRQ overlaps

    /node-tuning:analyze-node-tuning --sosreport /tmp/sosreport --max-irq-samples 5
    

Arguments:

  • --sosreport: Path to an extracted sosreport directory to analyze instead of the live filesystem.
  • --format: Output format (markdown default or json for structured data).
  • --output: Optional file path where the helper writes the report.
  • --max-irq-samples: Maximum number of IRQ affinity overlaps to include in the output (default 15).
  • --proc-root: Override path to the procfs tree when auto-detection is insufficient.
  • --sys-root: Override path to the sysfs tree when auto-detection is insufficient.
  • --node: OpenShift node name to analyze via oc debug node/<name> when direct access is not possible.
  • --kubeconfig: Path to the kubeconfig file used for oc debug; relies on the current oc context when omitted.
  • --oc-binary: Path to the oc binary (defaults to $OC_BIN or oc).
  • --keep-snapshot: Preserve the temporary directory produced from oc debug (snapshots or sosreports) for later inspection.
  • --collect-sosreport: Trigger sosreport via oc debug node/<name>, download the archive, and analyze the extracted contents automatically (default behavior whenever --node is supplied and no other source is chosen).
  • --no-collect-sosreport: Disable the default sosreport workflow when --node is supplied, falling back to the raw /proc//sys snapshot.
  • --sosreport-output: Directory where downloaded sosreport archives and their extraction should be placed (defaults to a temporary directory).
  • --toolbox-image: Override the container image that toolbox pulls when collecting sosreport (defaults to registry.redhat.io/rhel9/support-tools:latest or TOOLBOX_IMAGE env).
  • --sosreport-arg: Append an additional argument to the sosreport command (repeatable).
  • --skip-default-sosreport-flags: Do not include the default OpenShift-focused sosreport plugins/collectors; only use values supplied via --sosreport-arg.

Name

node-tuning:generate-tuned-profile

Synopsis

/node-tuning:generate-tuned-profile [profile-name] [--summary TEXT] [--include VALUE ...] [--sysctl KEY=VALUE ...] [--match-label KEY[=VALUE] ...] [options]

Description

The node-tuning:generate-tuned-profile command streamlines creation of tuned.openshift.io/v1 manifests for the OpenShift Node Tuning Operator. It captures the desired Tuned profile metadata, tuned daemon configuration blocks (e.g. [sysctl], [variables], [bootloader]), and recommendation rules, then invokes the helper script at plugins/node-tuning/skills/scripts/generate_tuned_profile.py to render a ready-to-apply YAML file.

Use this command whenever you need to:

  • Bootstrap a new Tuned custom profile targeting selected nodes or machine config pools
  • Generate manifests that can be version-controlled alongside other automation
  • Iterate on sysctl, bootloader, or service parameters without hand-editing multi-line YAML

The generated manifest follows the structure expected by the cluster Node Tuning Operator:

apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: <profile-name>
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
  - data: |
      [main]
      summary=...
      include=...
      ...
    name: <profile-name>
  recommend:
  - machineConfigLabels: {...}
    match:
    - label: ...
      value: ...
    priority: <priority>
    profile: <profile-name>

Implementation

  1. Collect inputs

    • Confirm Python 3.8+ is available (python3 --version).
    • Gather the Tuned profile name, summary, optional include chain, sysctl values, variables, and any additional section lines (e.g. [bootloader], [service]).
    • Determine targeting rules: either --match-label entries (node labels) or --machine-config-label entries (MachineConfigPool selectors).
    • Decide whether an accompanying MachineConfigPool (MCP) workflow is required for kernel boot arguments (see Advanced Workflow below).
    • Use the helper's --list-nodes and --label-node flags when you need to inspect or label nodes prior to manifest generation.
  2. Build execution workspace

    • Create or reuse .work/node-tuning/<profile-name>/.
    • Decide on the manifest filename (default tuned.yaml inside the workspace) or provide --output to override.
  3. Invoke the generator script

    • Run the helper with the collected switches:
      bash
      python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
        --profile-name "$PROFILE_NAME" \
        --summary "$SUMMARY" \
        --include openshift-node \
        --sysctl net.core.netdev_max_backlog=16384 \
        --variable isolated_cores=1 \
        --section bootloader:cmdline_ocp_realtime=+systemd.cpu_affinity=${not_isolated_cores_expanded} \
        --machine-config-label machineconfiguration.openshift.io/role=worker-rt \
        --match-label tuned.openshift.io/elasticsearch="" \
        --priority 25 \
        --output ".work/node-tuning/$PROFILE_NAME/tuned.yaml"
      
    • Use --dry-run to print the manifest to stdout before writing, if desired.
  4. Validate output

    • Inspect the generated YAML (yq e . .work/node-tuning/$PROFILE_NAME/tuned.yaml or open in an editor).
    • Optionally run oc apply --server-dry-run=client -f .work/node-tuning/$PROFILE_NAME/tuned.yaml to confirm schema compatibility.
  5. Apply or distribute

    • Apply to a cluster with oc apply -f .work/node-tuning/$PROFILE_NAME/tuned.yaml.
    • Commit the manifest to Git or attach to automated pipelines for deployment.

Advanced Workflow: Huge Pages with a Dedicated MachineConfigPool

Use this workflow when enabling huge pages or other kernel boot parameters that require coordinating the Node Tuning Operator with the Machine Config Operator while minimizing reboots.

  1. Label target nodes

    • Preview candidates: python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py --list-nodes --node-selector "node-role.kubernetes.io/worker" --skip-manifest.
    • Label workers with the helper (repeat per node):
      bash
      python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
        --label-node ip-10-0-1-23.ec2.internal:node-role.kubernetes.io/worker-hp= \
        --overwrite-labels \
        --skip-manifest
      
    • Alternatively run oc label node <node> node-role.kubernetes.io/worker-hp= directly if you prefer the CLI.
  2. Generate the Tuned manifest

    • Include bootloader arguments via the helper script:
      bash
      python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \
        --profile-name "openshift-node-hugepages" \
        --summary "Boot time configuration for hugepages" \
        --include openshift-node \
        --section bootloader:cmdline_openshift_node_hugepages="hugepagesz=2M hugepages=50" \
        --machine-config-label machineconfiguration.openshift.io/role=worker-hp \
        --priority 30 \
        --output .work/node-tuning/openshift-node-hugepages/hugepages-tuned-boottime.yaml
      
    • Review the [bootloader] section to ensure the kernel arguments match the desired configuration (e.g. kernel-rt, huge pages, additional sysctls).
  3. Author the MachineConfigPool manifest

    • Create .work/node-tuning/openshift-node-hugepages/hugepages-mcp.yaml with:
      apiVersion: machineconfiguration.openshift.io/v1
      kind: MachineConfigPool
      metadata:
        name: worker-hp
        labels:
          worker-hp: ""
      spec:
        machineConfigSelector:
          matchExpressions:
            - key: machineconfiguration.openshift.io/role
              operator: In
              values:
                - worker
                - worker-hp
        nodeSelector:
          matchLabels:
            node-role.kubernetes.io/worker-hp: ""
      
  4. Apply manifests (optional --dry-run)

    • oc apply -f .work/node-tuning/openshift-node-hugepages/hugepages-tuned-boottime.yaml
    • oc apply -f .work/node-tuning/openshift-node-hugepages/hugepages-mcp.yaml
    • Watch progress: oc get mcp worker-hp -w
  5. Verify results

    • Confirm huge page allocation after the reboot: oc get node <node> -o jsonpath="{.status.allocatable.hugepages-2Mi}"
    • Inspect kernel arguments: oc debug node/<node> -q -- chroot /host cat /proc/cmdline

Return Value

  • Success: Path to the generated manifest and the profile name are returned to the caller.
  • Failure: Script exits non-zero with stderr diagnostics (e.g. invalid KEY=VALUE pair, missing labels, unwritable output path).

Examples

  1. Realtime worker profile targeting worker-rt MCP

    /node-tuning:generate-tuned-profile openshift-realtime \
      --summary "Custom realtime tuned profile" \
      --include openshift-node --include realtime \
      --variable isolated_cores=1 \
      --section bootloader:cmdline_ocp_realtime=+systemd.cpu_affinity=${not_isolated_cores_expanded} \
      --machine-config-label machineconfiguration.openshift.io/role=worker-rt \
      --output .work/node-tuning/openshift-realtime/realtime.yaml
    
  2. Sysctl-only profile matched by node label

    /node-tuning:generate-tuned-profile custom-net-tuned \
      --summary "Increase conntrack table" \
      --sysctl net.netfilter.nf_conntrack_max=262144 \
      --match-label tuned.openshift.io/custom-net \
      --priority 18
    
  3. Preview manifest without writing to disk

    /node-tuning:generate-tuned-profile pidmax-test \
      --summary "Raise pid max" \
      --sysctl kernel.pid_max=131072 \
      --match-label tuned.openshift.io/pidmax="" \
      --dry-run
    

Arguments:

  • $1 (profile-name): Name for the Tuned profile and manifest resource.
  • --summary: Required summary string placed in the [main] section.
  • --include: Optional include chain entries (multiple allowed).
  • --main-option: Additional [main] section key/value pairs (KEY=VALUE).
  • --variable: Add entries to the [variables] section (KEY=VALUE).
  • --sysctl: Add sysctl settings to the [sysctl] section (KEY=VALUE).
  • --section: Add lines to arbitrary sections using SECTION:KEY=VALUE.
  • --machine-config-label: MachineConfigPool selector labels (key=value) applied under machineConfigLabels.
  • --match-label: Node selector labels for the recommend[].match[] block; omit =value to match existence only.
  • --priority: Recommendation priority (integer, default 20).
  • --namespace: Override the manifest namespace (default openshift-cluster-node-tuning-operator).
  • --output: Destination file path; defaults to <profile-name>.yaml in the current directory.
  • --dry-run: Print manifest to stdout instead of writing to a file.
  • --skip-manifest: Skip manifest generation; useful when only listing or labeling nodes.
  • --list-nodes: List nodes via oc get nodes (works with --node-selector).
  • --node-selector: Label selector applied when --list-nodes is used.
  • --label-node: Apply labels to nodes using NODE:KEY[=VALUE] notation; repeatable.
  • --overwrite-labels: Allow overwriting existing labels when labeling nodes.
  • --oc-binary: Path to the oc executable (defaults to $OC_BIN or oc).

Sponsors

Details

Marketplace
openshift-eng/ai-helpers
Source
plugins/node-tuning
Category
Debugging
Keywords
tuned, node-tuning, performance, profiles

More from openshift-eng/ai-helpers

All 56