GCP Playground: cannot create namespace in GKE

After creating a basic k8s cluster in the GCP Playground, I'm trying to create a namespace in cloud shell as follows:

kubectl create namespace my-namespace

I get the following error:

W0702 07:12:04.787955     975 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
Error from server (Forbidden): namespaces is forbidden: User "[email protected]" cannot create resource "namespaces" in API group "" at the cluster scope: requires one of ["container.namespaces.create"] permission(s).

We don't have access to "IAM & Admin" in the clgcporg2-xxx project created by playground. How should I proceed to grant "container.namespaces.create" permission to user "[email protected]" ?

Hi @philippe.lawson ,
Apologies for this inconvenience. We are looking into it.

Regards,
KodeKloud Support

Actually the GKE cluster is almost unusable, cannot create services, comfigmaps, autoscaler, secrets, Role, rolbinding, clusterrole, clusterrolebinding,etc.
Cannot get ns…

Yes, we will get this fixed. I will update you once it gets fixed.

Regards,

Hi @philippe.lawson ,
Can you please check again? We have pushed some updates and I cross-checked and I am able to create resources.
Let me know if you are seeing/facing any issues.

Best Regards,
KodeKloud Support

Hello,
I was able run my tests, thank you.
By the way I’d like to take this opportunity to thank you guys for releasing Playgrounds. This is really useful!

1 Like

Most Welcome!! :blush: :+1:

Having very similar issue just a different resource.

k create -f example-voting-app-kubernetes/redis-service.yaml

Error from server (Forbidden): error when creating "example-voting-app-kubernetes/redis-service.yaml": services is forbidden: User "[email protected]" cannot create resource "services" in API group "" in the namespace "default": requires one of ["container.services.create"] permission(s).

Hi @thedzy,
Thanks for highlighting this. The team is checking this. I will update you once it gets resolved.

Regards,