SUS-1704: Support bundle size guard (edge only)#36
Open
ramganesh-spectro wants to merge 1 commit into
Open
Conversation
Caps log lines and per-file bytes with a warnings manifest, replaces cluster-info dump with an explicit resources tree, and preserves sparse files via tar --sparse.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bounds
support-bundle-edge.shcollection on chatty edge nodes.Replaces
kubectl cluster-info dumpwith explicit Kubernetes resource andcurrent pod-log collection.
Scope:
support-bundle-edge.shonly.support-bundle-infra.shfollowsin a separate PR.
What changed
journalctl,crictl, and current/previouskubectl logsat500,000 lines by default.
-lremains tunable and now applies evenwhen journal time filters are set.
/var/log,/var/log/spectrocloud, and/var/log/podsfiles at 500 MiB by default.
-m <MiB>overrides the CLI cap;MAX_FILE_BYTESremains a byte-level environment override.Skipped files are recorded in
collection-warnings.txt.tar --sparsewhen available to avoid sparse-file archiveinflation.
kubectl cluster-info dump. Resource YAML is collected underk8s/cluster-resources/, includingreplicationcontrollers; currentpod logs are collected under
k8s/pod-logs-current/.Testing
Paired baseline-versus-after testing passed on a k3s edge cluster
(Kairos v4.0.3, k3s v1.32.13, GNU tar 1.34): line caps, file caps,
manifest format,
-mvalidation/semantics, sparse-tar fallback, retainedtext filtering, current pod-log caps, and ReplicaController coverage.
Kubeadm and Canonical Kubernetes were not exercised. The changed helper
and cap logic is distro-agnostic, but one paired run on each remains
recommended before broad rollout.
Ticket
SUS-1704