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

Retry with timeout during boot to wait for kong to start up #766

Closed
hbagdi opened this issue Jul 8, 2020 · 0 comments · Fixed by #771
Closed

Retry with timeout during boot to wait for kong to start up #766

hbagdi opened this issue Jul 8, 2020 · 0 comments · Fixed by #771

Comments

@hbagdi
Copy link
Member

hbagdi commented Jul 8, 2020

Multiple users have reported that the controller goes into a crash loop backoff state if kong container doesn't start up before the controller or if there is delay in startup of the kong container.

Add in a retry with back-off and timeout (30s) to the initial API call that the controller makes to Kong. This should result in more pods being started without any restarts.

See #761 and multiple posts on Kong Nation.
@hbagdi hbagdi mentioned this issue Jul 8, 2020
Closed
@yuchunyu97 yuchunyu97 mentioned this issue Jul 10, 2020
Merged
hbagdi pushed a commit that referenced this issue Jul 21, 2020
@yuchunyu97
fix: retry initial API call to kong during startup
31c68f6 
If k8s is starting up kong or if kong is taking a while to start up for any reason,
the ingress controller process would exit immediately since it can't
establish a connection with Kong. With this change, the controller performs
retries and then exits.

Fixes #761
Fixes #766
From #771
@mflendrich mflendrich mentioned this issue Aug 11, 2020
Merged
hbagdi pushed a commit that referenced this issue Aug 11, 2020
@mflendrich
feat: add timeout to initial connection to Kong (#799)
fc5de5c 
Fix #766
@hbagdi hbagdi closed this as completed Aug 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: solve the restart caused by kong not starting
1 participant
@hbagdi