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

Bad Gateway on Deployment #55

Closed
BugRoger opened this issue Sep 22, 2017 · 3 comments
Closed

Bad Gateway on Deployment #55

BugRoger opened this issue Sep 22, 2017 · 3 comments

Comments

@BugRoger
Copy link
Contributor

Only 1 ApiServer causes downtime on deployment?

@stale
Copy link

stale bot commented Oct 22, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 22, 2017
@BugRoger
Copy link
Contributor Author

This was fixed by adding maxSurge and minUnavailable options to the deployment of the apiserver. With only 1 replica the default settings cause a downtime when deploying a new image.

This caused a prominent error in the deployment pipelines: No consumer for text/html. The problem here was actually the parallel deployment of the admin apiserver and concurrently fetching credentials for it in the staging pipeline. Fix now.

In addition this issue surfaced a problem with nginx' default backend. It responds with text/html error pages even if json is requested. Would be great if it responded in json for the various (javascript) clients.

@BugRoger
Copy link
Contributor Author

See #80

@databus23 databus23 removed the wontfix label Oct 26, 2017
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