elastic / elastic/eck-diagnostics

Allow more targeted runs of eck-diagnostics for large environments

Open
#81 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
29
Forks
21
Avg merge
3d 13h
Merged PRs (30d)
10

Description

We should consider allowing users to target the diagnostic run to individual resources rather than whole namespaces as the size of the diagnostic archive can get very bit in larger deployments of ECK

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by locating the eck-diagnostics command that selects namespaces and review how diagnostic archives are assembled. Define the resource-level targeting behavior and verify that a large-environment run collects only the requested resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.