Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve warning messages in kuma-validation to help diagnose kuma-cni issues #13335

Open
jijiechen opened this issue Apr 7, 2025 · 0 comments · May be fixed by #13336
Open

Improve warning messages in kuma-validation to help diagnose kuma-cni issues #13335

jijiechen opened this issue Apr 7, 2025 · 0 comments · May be fixed by #13336
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@jijiechen
Copy link
Member

Description

Right now, we blocks the container from starting when the kuma-validation container fails, and we are not telling the user what to do in this case: this is usually because this cluster has kuma-cni enabled and transparent proxy is not correctly setup in the pod.

The current console messages are, they are not helpful enough to diagnose issues:

kuma-validation 2025-03-31T04:22:38.964Z INFO validator starting iptables validation  
kuma-validation 2025-03-31T04:22:38.964Z INFO validator listening on 127.0.0.1:15006  
kuma-validation 2025-03-31T04:22:38.965Z INFO validator [WARNING] client failed to connect to server: dial tcp 127.0.0.1:0->127.0.0.6:29517: connect: connection refused 
kuma-validation 2025-03-31T04:22:39.965Z INFO validator [WARNING] client failed to connect to server: dial tcp 127.0.0.1:0->127.0.0.6:29517: connect: connection refused 
kuma-validation 2025-03-31T04:22:40.966Z INFO validator [WARNING] client failed to connect to server: dial tcp 127.0.0.1:0->127.0.0.6:29517: connect: connection refused 
kuma-validation 2025-03-31T04:22:41.966Z INFO validator [WARNING] client failed to connect to server: dial tcp 127.0.0.1:0->127.0.0.6:29517: connect: connection refused
@jijiechen jijiechen added kind/feature New feature triage/pending This issue will be looked at on the next triage meeting labels Apr 7, 2025
@jijiechen jijiechen changed the title Improve warning message in kuma-validation to help diagnose kuma-cni issues Improve warning messages in kuma-validation to help diagnose kuma-cni issues Apr 7, 2025
@slonka slonka linked a pull request Apr 7, 2025 that will close this issue
Open
@Automaat Automaat added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(logs): add more info to kuma-validation failure logs slonka/kuma
2 participants
@jijiechen @Automaat