-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
useless and misleading message in Config.fromKubeconfig #5166
Comments
This goes back to one of the initial commits in the project (#237, #142, #93) #92 It does seem like an outdated solution, we should find a proper way to forward any error messages (real). Also, this looks like it was probably consumed by a downstream project that very likely is no longer active. |
I'd vote for removing what is set in the config and deprecating getErrorMessages. The kubernetes status or what's in HttpStatusMessage should cover the bases well enough. |
…'s `errorMessages` and deprecate it (fabric8io#5166) + Remove opinionated status code to message mappings from Config + Deprecate Config.errorMessages field in favor of kubernetes status + Update OperationSupport to only rely on Kubernetes status for error messages Signed-off-by: Rohan Kumar <[email protected]>
…'s `errorMessages` and deprecate it (fabric8io#5166) + Remove opinionated status code to message mappings from Config + Deprecate Config.errorMessages field in favor of kubernetes status + Update OperationSupport to only rely on Kubernetes status for error messages Signed-off-by: Rohan Kumar <[email protected]>
…'s `errorMessages` and deprecate it (fabric8io#5166) + Remove opinionated status code to message mappings from Config + Deprecate Config.errorMessages field in favor of kubernetes status + Update OperationSupport to only rely on Kubernetes status for error messages Signed-off-by: Rohan Kumar <[email protected]>
…'s `errorMessages` and deprecate it (fabric8io#5166) + Remove opinionated status code to message mappings from Config + Deprecate Config.errorMessages field in favor of kubernetes status + Update OperationSupport to only rely on Kubernetes status for error messages Signed-off-by: Rohan Kumar <[email protected]>
…'s `errorMessages` and deprecate it (#5166) + Remove opinionated status code to message mappings from Config + Deprecate Config.errorMessages field in favor of kubernetes status + Update OperationSupport to only rely on Kubernetes status for error messages Signed-off-by: Rohan Kumar <[email protected]>
kubernetes-client/kubernetes-client-api/src/main/java/io/fabric8/kubernetes/client/Config.java
Line 751 in 14833da
kubernetes-client/kubernetes-client-api/src/main/java/io/fabric8/kubernetes/client/Config.java
Line 547 in 14833da
is there any reason to add this message?
The text was updated successfully, but these errors were encountered: