You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have the same host analyser defined in two different specs they end up showing twice when I run kubectl support-bundle spec0 spec1. The same does not happen with a regular analyser, only with host analysers. It seems like the same deduplication applied for analysers is not applied for host analysers.
Expected Behavior
My duplicated host analyser to show up only once.
Steps To Reproduce
Create two specs with the same host analyser:
apiVersion: troubleshoot.sh/v1beta2kind: SupportBundlemetadata:
name: embedded-cluster-host-support-bundlespec:
hostCollectors:
- memory: {}hostAnalyzers:
- memory:
checkName: Amount of Memoryoutcomes:
- warn:
when: "< 2G"message: At least 2G of memory is recommended
- pass:
message: The system has at least 2G of memory
Then run the support-bundle passing both specs:
kubectl support-bundle spec0.yaml spec1.yaml
With the --dry-run flag I can see that the same host analyser is duplicated in the merged result.
The text was updated successfully, but these errors were encountered:
ricardomaraschini
changed the title
Host collectors are not deduplicating during multiple spec merges
Host analysers are not deduplicating during multiple spec merges
Feb 22, 2024
Bug Description
If I have the same host analyser defined in two different specs they end up showing twice when I run
kubectl support-bundle spec0 spec1
. The same does not happen with a regular analyser, only with host analysers. It seems like the same deduplication applied for analysers is not applied for host analysers.Expected Behavior
My duplicated host analyser to show up only once.
Steps To Reproduce
Create two specs with the same host analyser:
Then run the support-bundle passing both specs:
With the
--dry-run
flag I can see that the same host analyser is duplicated in the merged result.The text was updated successfully, but these errors were encountered: