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

Cluster - KubernetesProvider #1017

Closed
rogeralsing opened this issue Jun 2, 2021 · 4 comments · Fixed by #1018
Closed

Cluster - KubernetesProvider #1017

rogeralsing opened this issue Jun 2, 2021 · 4 comments · Fixed by #1018

Comments

@rogeralsing
Copy link
Contributor

Potential bug in KubernetesProvider.
We have observed pods not getting new topology from the KubernetesProvider.

This could potentially be any of the following issues:

  • Outdated Kubernetes client, the issue was seen in 0.17.0
  • Bug in KubernetesProvider, e.g. the watch for some reason hangs
  • Some form of deadlock in MemberList when processing topology changes
  • Other?

Actions.

  • More logging and added timeouts for KubernetesProvider watcher.
  • Make it possible to stream event stream data to the outside world for diagnostics.
@rogeralsing
Copy link
Contributor Author

Possibly related kubernetes-client/csharp#533

@rogeralsing
Copy link
Contributor Author

Potentially an issue in AKS itself:
Azure/AKS#1755

Seems to have been fixed in later releases

@rogeralsing
Copy link
Contributor Author

There could be multiple reasons for what we are seeing, keeping this open until we have verified of the issue goes away with the new patch

@rogeralsing
Copy link
Contributor Author

Multiple fixes went into 0.20.0. repoen if issues shows up again

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

Successfully merging a pull request may close this issue.

1 participant