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

Make KubernetesClientException more detailed so that we can get information about what went wrong #3491

Closed
metacosm opened this issue Sep 23, 2021 · 0 comments · Fixed by #3492
Assignees
Labels

Comments

@metacosm
Copy link
Collaborator

metacosm commented Sep 23, 2021

It would be interesting to have the detail of the resource(s) that caused a KubernetesClientException so that more accurate decisions can be made in client code.

@metacosm metacosm self-assigned this Sep 23, 2021
@metacosm metacosm changed the title Make KubernetesException more detailed so that we can get information about what went wrong Make KubernetesClientException more detailed so that we can get information about what went wrong Sep 23, 2021
metacosm added a commit that referenced this issue Sep 23, 2021
If the exception occurred from an HTTP request, use that information
to populate information about the target resource.

Fixes #3491
metacosm added a commit that referenced this issue Sep 23, 2021
If the exception occurred from an HTTP request, use that information
to populate information about the target resource.

Fixes #3491
metacosm added a commit that referenced this issue Sep 23, 2021
If the exception occurred from an HTTP request, use that information
to populate information about the target resource.

Fixes #3491
manusa pushed a commit that referenced this issue Sep 23, 2021
If the exception occurred from an HTTP request, use that information
to populate information about the target resource.

Fixes #3491
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant