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

Init container errors are not informative #103

Closed
shaikatz opened this issue Jan 22, 2019 · 0 comments · Fixed by #102
Closed

Init container errors are not informative #103

shaikatz opened this issue Jan 22, 2019 · 0 comments · Fixed by #102
Labels
enhancement New feature or request

Comments

@shaikatz
Copy link
Contributor

Currently when decrypt API returns 400 the user see
Failed to run init container: Error: Request failed with status code 400

Which request? to where? need to provide more info.
@shaikatz shaikatz mentioned this issue Jan 22, 2019
Merged
@omerlh omerlh added the enhancement New feature or request label Jan 22, 2019
@shaikatz shaikatz changed the title Init container error are not informative Init container errors are not informative Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

better error handling for the init container Soluto/kamus
2 participants
@omerlh @shaikatz