value must not be falsy

[cavus700]

---

App Version 1.0.11-beta
Arch: x64
Platform: linux
osRelease: 6.10.7-100.fc39.x86_64
Locale: en-US
ErrorMessage: value must not be falsy

Everytime I want to open the logs or a shell for a pod I see this error message and my K8Studio requires a restart.

[mo-othman]

Hi @cavus700

We are investing the issue and will keep you updated

just one question, what's the kubectl version?

[cavus700]

Thank you :)
I am using these versions:

Client Version: v1.29.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3

[mo-othman]

Hi @cavus700, we are trying to reproduce the issue

Can you try running kubectl logs -f {POD_NAME} in the terminal and let us know if it works?
by using K8Studio terminal and your terminal as well

Thanks

[cavus700]

Hello @mo-othman,
in my terminal I can use this command and see all logs but in K8Studio I can't try it because I see the same error when I just try to open a terminal.
Could it be related to my permissions? I am not allowed to access the namespace resource in the cluster and added the namespace manually in the UI.

K8Studio Log:

Error: User needs to have access to the namespaces resource.

[mo-othman]

I would like to confirm which error are you getting

User needs to have access to the namespaces resource. or value must not be false?

[cavus700]

I get both erros but "value must not be falsy" is my problem. In our cluster users are not allowed to access the namespace resource so I added it manually in the K8Studio settings.
My guess is that "value must not be falsy" could be related to the fact, that I can not access the namespace resource.

[mo-othman]

Thanks for the update @cavus700

We are going to do another set up with limited access and recheck again

[cavus700]

Hello @mo-othman,
were you able to reproduce the error or is there anything else I could do to help you?

[guiqui]

Will you be open to doing a short call to troubleshoot the issue?

[cavus700]

Hello @guiqui,
I tried to use the newest version of K8Studio and I am able to see the logs of a pod now :) Unfortunately I still encounter the same bug when I try to open the terminal of a pod.

---

App Version 3.0.6-beta
Arch: x64
Platform: linux
osRelease: 6.13.5-200.fc41.x86_64
Locale: en-US
ErrorMessage: value must not be falsy

Not sure if this matters but all of my pods have some security constraints:

spec:
    containers:
        -   ...
            securityContext:
                readOnlyRootFilesystem: true
securityContext:
    runAsUser: 1001
    runAsGroup: 1001
    runAsNonRoot: true
    fsGroup: 1001
    fsGroupChangePolicy: OnRootMismatch