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

Monitoring kubectl for changes to integrations misses transition to error state #937

Closed
bfitzpat opened this issue Sep 13, 2019 · 3 comments

Comments

@bfitzpat
Copy link
Contributor

So I've started looking at auto-refresh in the tooling and hit upon a fun little issue.

If I use "kubectl get integrations -w" to watch for changes to running integrations, I am finding that
starting new integrations works great if they work all the way through Building Kit into Running
but I'm not getting notified when things go from Building Kit to Error.

Is that a bug by chance?

Will there eventually be some additional kamel cli-based health/updates that we can monitor in a similar way?

@bfitzpat
Copy link
Contributor Author

Looks like "kubectl get" has a timeout as well. If nothing in the system changes after a few seconds, the thread is shut down. Not sure if there's a way to keep that alive indefinitely while the tooling is running?

@bfitzpat
Copy link
Contributor Author

Looks like the same issue is being seen here - #906

@bfitzpat
Copy link
Contributor Author

Actually it was a watch timeout issue on my side, not the same issue as #906 - worked around the timeout and now we see it transition from Building Kit to Error eventually. Closing.

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

1 participant