Handle config was not read due some issue and display what was the error instead of generic deserialization error

[LeszekKalibrate]

In file, line https://github.com/kubernetes-client/csharp/blob/master/src/KubernetesClient/KubernetesClientConfiguration.ConfigFile.cs#L572
There is no check that the output was successful, so when it fails we get just a dump deserialization error.

Can a simple check like string.IsNulOrEmpty be added and then if yes , throw an exception, but with the text from error output?

Sometimes I get randomly that error, and today it was due to personal access token expired, but deserialization error for an empty string does not give any hint.
Thank you.

Using:
var kubernetesClientConfig = KubernetesClientConfiguration.BuildDefaultConfig(); to read from kube/.config file.

[tg123]

"" would trigger an exception too, may i know why it is necessary to check empty string?

[LeszekKalibrate]

var responseObject = KubernetesJson.Deserialize<ExecCredentialResponse>(output.ToString());

to
var expectedJsonConfiguration = output.ToString();
if (string.IsNullOrEmpty(expectedJsonConfiguration) //failed, like due to expired personal access token
{
throw new KubeConfigException($"external exec failed due to an error {errorOutput}");
}

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten