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.

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

Networking probes #991

Open
aojea opened this issue Nov 26, 2024 · 4 comments
Open

Networking probes #991

aojea opened this issue Nov 26, 2024 · 4 comments
Assignees

Comments

@aojea
Copy link
Member

aojea commented Nov 26, 2024

Talked with @danwinship offline, it will be nice to be able to report

  • Pod network problems
  • DNS cluster problems
  • Services problems

It should not be hard to provide some basic plugins that provide some basic checks, if we can figure out the best way to obtain the information needed

@aojea
Copy link
Member Author

aojea commented Nov 26, 2024

/cc @danwinship
/assign @aojea

@googs1025
Copy link
Member

googs1025 commented Dec 26, 2024

We currently have some pods such as cni network plug-ins, and we also want to detect its health status.

We now use custom plugins to detect whether a specific pod is alive. Perhaps HealthChecker should also support monitoring the status of a specific pod for inspection. 🤔

@aojea
Copy link
Member Author

aojea commented Dec 29, 2024

pods such as cni network plug-ins

why current Pod Probes are not valid?

@googs1025
Copy link
Member

Using pod probe can let us know whether the pod is alive, but it does not seem to convert to node condition. Because we have a custom daemonset program, we want when daemonset agents are crashed, they will not be scheduled to this node. If this feature is not provided, we need to implement similar features ourselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants