Error when show log or run exec

[YuriiKosiy]

---

App Version 2.1.0
Arch: x64
Platform: linux
osRelease: 5.15.0-136-generic
Locale: uk
ErrorMessage: value must not be falsy

[mo-othman]

Hi @YuriiKosiy,

Just want to confirm, Are kubectl commands like logs and exec working for you both in your local terminal and within the K8Studio terminal?

[YuriiKosiy]

Hello @mo-othman ,

Yes, I can confirm:

• kubectl logs and exec commands work perfectly fine in my local terminal.
• The issue only seems to occur within the K8Studio terminal, specifically with the newer version.
• I rolled back to the previous version of K8Studio, and both logs and exec commands are working normally there.

But...

It seems the issue might be related to how K8Studio v2.1.0 handles contexts, especially in my environment with multiple GKE clusters across different Google Cloud accounts and projects.

Here's the sequence:

1. Upgraded K8Studio to 2.1.0 -> exec/logs failed for the cluster I was working with.
2. Rolled back K8Studio -> exec/logs worked.
3. Then, I switched my active gcloud configuration to point specifically to the account/project containing the GKE cluster I needed.
4. Re-installed K8Studio v2.1.0.
5. Now, exec/logs are working correctly in K8Studio 2.1.0 for the cluster associated with the currently active gcloud configuration.

It appears the initial problem might have been K8Studio 2.1.0 picking up stale credentials or the context from one of my inactive GKE clusters/accounts after the upgrade. Forcing the correct gcloud context and reinstalling resolved it for the active cluster.

However, this seems to imply a potential workflow change. Does this mean that to use K8Studio 2.1.0 with clusters in different accounts/projects, I now need to explicitly switch the active gcloud configuration each time? It seems less convenient than potentially switching contexts directly within the tool or having it correctly use the context selected from the kubeconfig regardless of the active gcloud setting."

[mo-othman]

Hi @YuriiKosiy
Thanks for the detailed breakdown, It's helpful

You definitely shouldn’t need to manually switch the active gcloud configuration each time, It's a bug
We are investigating the issue and I will keep u updated

[mo-othman]

Hi @YuriiKosiy

Following up

Are you currently able to reproduce the issue on your end? I’ve attempted it several times but haven’t been able to replicate the behavior so far.

Also, if you're available for a brief call to review it together, I’d be happy to coordinate a time that works for both of us.