rancher / rancher/support-bundle-kit

Unable to run Support Bundle Kit if the cluster has some custom CRDs.

Open
#171 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
24
Forks
43
Avg merge
1d 15h
Merged PRs (30d)
6

Description

If the Harvester cluster has some CRDs like Kasten, we must completely remove all YAMLs and folders that has references to these CRDs. Otherwise, the sbk will always crash:

FATA[0016] Error loading cluster scoped objects error looking up GVR no matches for kind "RetireAction" in version "actions.kio.kasten.io/v1alpha1" for object &{map[apiVersion:actions.kio.kasten.io/v1alpha1 kind:RetireAction metadata:map[annotations:map[sim.harvesterhci.io/creationTimestamp:2025-07-15T07:09:46Z] creationTimestamp:2025-07-15T07:09:46Z name:retire-scheduled-znlc9-s68zz uid:b0833b7a-614a-11f0-a156-4e24ef7f4220] spec:map[scheduledTime:2025-07-15T07:09:46Z subject:map[apiVersion:internals.kio.kasten.io/v1alpha1 kind:Manifest name:5b4c5973-60aa-11f0-a156-4e24ef7f4220]] status:map[endTime:2025-07-15T07:09:54Z progress:100 restorePoint:map[] result:map[] startTime:2025-07-15T07:09:46Z state:Complete]]}

FATA[0108] Error loading cluster scoped objects error looking up GVR no matches for kind "Passkey" in version "vault.kio.kasten.io/v1alpha1" for object &{map[apiVersion:vault.kio.kasten.io/v1alpha1 kind:Passkey metadata:map[annotations:map[sim.harvesterhci.io/creationTimestamp:2025-07-04T12:08:04Z] creationTimestamp:2025-07-04T12:08:04Z name:k10MasterKey uid:89be8de1-58cf-11f0-8bd8-ba4018a12a8f] spec:map[secret:map[name:k10-cluster-passphrase namespace:kasten-io]] status:map[state:Added to Catalog valid:true]]} 

and others

To remove kasten yamls:
find ./support-bundle-folder -type d -iname '*kasten*' -exec rm -rf {} +

The same occur with other CRDs. (There is one called flow something, but I do not remember the exactly name of this one, I will update once I remember).

I wonder if we can improve the sbk to work with these CRDs.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with a support bundle containing Kasten or another unregistered CRD, then trace the cluster-scoped object loading path that reports “error looking up GVR.” Compare the generated bundle with the issue’s find-based cleanup workaround; done means Support Bundle Kit completes without crashing when custom-CRD YAMLs are present.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.