-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hubble/recorder: Sanitize pcap filename #18612
hubble/recorder: Sanitize pcap filename #18612
Conversation
This removes any special characters from the generated pcap filename. This fixes a bug where we accidentally added a slash to the filename when we added support for the cluster name. This broke file creation, as file names cannot contain slashes. Fixes: 3203df9 ("hubble: Hubble node_name field should contain cluster name") Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
ff4926f
to
a25a479
Compare
/test Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment Job 'Cilium-PR-K8s-1.23-kernel-net-next' has 2 failures but they might be new flakes since it also hit 1 known flakes: #18566 (96.68) |
/test-1.23-net-next |
GKE test failure (linked above) is unrelated, as the code modified by this PR is not active in that test suite at all and doesn't affect connectivity either. Marking ready to merge. |
Marking for backport to v1.10 too. Sanitizing the file path is something we should always do. |
This removes any special characters from the generated pcap filename.
This fixes a bug where we accidentally added a slash to the filename
when we added support for the clustername. This broke file creation, as
file names cannot contain slashes.
Fixes: 3203df9 ("hubble: Hubble node_name field should contain cluster name")
Signed-off-by: Sebastian Wicki sebastian@isovalent.com