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

Update readiness condition based on new Camel health check format #2886

Closed
astefanutti opened this issue Jan 18, 2022 · 3 comments · Fixed by #3310
Closed

Update readiness condition based on new Camel health check format #2886

astefanutti opened this issue Jan 18, 2022 · 3 comments · Fixed by #3310
Assignees
Milestone

Comments

@astefanutti
Copy link
Member

The parsing of the health check results from the integration Pod(s) readiness endpoint(s) should be adapted once apache/camel#6779 is pulled.

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@tadayosi
Copy link
Member

OK, now I'm investigating why health_test.go always fails on CI. Is this the reason why it always does? If so, I'm taking care of it.

@squakez
Copy link
Contributor

squakez commented May 27, 2022

Very very probably :)

tadayosi added a commit to tadayosi/camel-k that referenced this issue May 27, 2022
tadayosi added a commit to tadayosi/camel-k that referenced this issue May 30, 2022
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue May 31, 2022
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue May 31, 2022
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue May 31, 2022
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue May 31, 2022
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue Jun 1, 2022
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.

4 participants