Problem

The kor crd command was failing with the error "the server could not find the requested resource" on systems with certain CRD configurations, particularly when CRDs have multiple versions where the first version is not served.

user@k3s:~# kor crd
Failed to process crds: the server could not find the requested resource

Root Cause

The code in processCrds() was incorrectly using crd.Spec.Versions[0].Name to determine which API version to query for CRD instances. This caused two issues:

1. Wrong version selection: The first version in the array might have Served: false, meaning it's not available via the API server
2. Overly strict error handling: Any error when querying instances would cause the entire command to fail

For example, a CRD might be defined as:

versions:
  - name: v1alpha1
    served: false    # Not available!
  - name: v1
    served: true     # This should be used

Solution

This PR fixes the issue by:

1. Finding the first served version: Iterates through crd.Spec.Versions to find a version where Served: true
2. Skipping CRDs with no served versions: If no served version is found, the CRD is skipped rather than causing a failure
3. Graceful error handling: If querying a CRD fails (e.g., API server doesn't recognize it), skip it instead of failing the entire command

Changes

• Modified processCrds() in pkg/kor/crds.go to properly select served versions
• Added TestProcessCrds() in pkg/kor/crds_test.go to verify the fix with multiple test scenarios

Testing

The new test validates:

• CRDs where the first version is not served (uses the first served version instead)
• CRDs with no served versions (properly skipped)
• CRDs with a served version (processed normally)

All existing tests continue to pass.

Fixes #[issue_number]

Fixes #503

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.