Skip to main content
Data Infrastructure Insights

Check Kubernetes collector currency

Contributors netapp-alavoie
PDFs

Use this recipe to identify Kubernetes clusters whose DII operator or collection components are outdated, disabled, or stale.

Note The DII MCP is a Preview feature and is therefore subject to change.

Prerequisites

  • Kubernetes collection is configured in the DII tenant.

  • Access to Kubernetes collector information.

Tools used

  • OperatorsManagement_getKubernetesCollectors

  • Optional: AcquisitionUnitsService_getAcquisitionUnits

  • Optional: CollectorService_getDataSources

Starter prompt

Review DII Kubernetes collector currency. Group clusters by overall status, identify outdated or disabled operators and components, and flag stale last-reported timestamps. Do not display internal addresses or UUIDs.

Agent workflow

  1. List Kubernetes collectors.

  2. Normalize each cluster into:

    • Up to date

    • Outdated

    • Disabled

    • Unknown

  3. Compare:

    • Operator version

    • Network Performance and Map component version

    • Change Analysis component version

  4. Convert the last-reported timestamp into the requested timezone.

  5. Flag clusters that have not reported within the agreed freshness threshold.

  6. Distinguish N/A from an outdated version:

    • N/A can mean the component is not installed, not enabled, or not applicable.

  7. If reporting is stale, inspect related acquisition-unit and collector status where available.

  8. Return a prioritized upgrade and investigation list.

Interpretation

  • Outdated: at least one installed component is behind the DII-expected version.

  • Disabled: collection is intentionally or administratively disabled.

  • Stale reporting: version data may not reflect the cluster's current state.

  • N/A: requires context; do not automatically classify it as a failure.

The tool reports versions and status. It does not perform upgrades.

Suggested output

  1. Cluster counts by status

  2. Outdated clusters ranked by reporting freshness

  3. Component-level version differences

  4. Disabled or unavailable components

  5. Recommended verification steps

Limits and privacy

  • Cluster names can be sensitive; use approved handling when sharing results.

  • Do not infer vulnerability exposure from version currency alone.

  • Validate upgrade compatibility and process outside this read-only workflow.

Follow-up prompts

Which clusters have an outdated operator and have not reported in the last hour?

Separate clusters with an outdated Change Analysis component from clusters where that component is unavailable.

For stale clusters, check whether the associated DII collection infrastructure is healthy.

Back to recipes