You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
calling skuber.api.Configuration.parseKubeconfigFile() throws an exception when kube config file has a GCP user without "cmd-args" and "cmd-path" (which are optional fields).
I couldn't find the official documentation, but I have witnessed cases where gcloud CLI did not add these fields when importing a new user and I can confirm these contexts were working properly without them using kubectl (probably since "gcloud" is in my path).
Note that this exception will be thrown even when not attempting to access the malformed context.
calling skuber.api.Configuration.parseKubeconfigFile() throws an exception when kube config file has a GCP user without "cmd-args" and "cmd-path" (which are optional fields).
Error thrown:
Caused by: java.util.NoSuchElementException: None.get
.skuber/client/src/main/scala/skuber/api/Configuration.scala
Lines 179 to 180 in c86bdfc
I couldn't find the official documentation, but I have witnessed cases where gcloud CLI did not add these fields when importing a new user and I can confirm these contexts were working properly without them using kubectl (probably since "gcloud" is in my path).
Note that this exception will be thrown even when not attempting to access the malformed context.
Suggested solution: providing fallback values to GcpCommand - cmd-args: "config config-helper --format=json", cmd-path: "gcloud". WDYT?
The text was updated successfully, but these errors were encountered: