Fabian Kramm

@john-deng thanks for creating this issue! Seems like your cluster was not available during that time or kiosk couldn't connect to it, what Kubernetes cluster are you using?

@john-deng yes the log message helps, however I'm afraid there is not much we can do on our side to avoid this, as kiosk requires interaction with the Kubernetes API...

@unbreakabl3 thanks for creating this issue! Yes, you are correct, spaces of an account are not deleted if an account is deleted. This might a feature we could add though.

@juv thanks for creating this issue! We'll add an option to make this configurable

@zeusro Hello! Kiosk is not a solution to filter any arbitrary cluster scoped resource, rather kiosk divides users by the namespaces they have access to and introduces a new resource...

@deuch while I see this could be helpful in some cases, I think there are some points that seem problematic to me: 1. How do you handle naming conflicts? If...

@deuch sorry, seems I missed your response. I'm not sure about the authorized namespaces field, since this would only work for helm chart templates were all resource names in the...

@deuch currently there is no official ETA for those CRDs, its still in the planning phase and there are some other things that are important as well as for example...

@cortex93 thanks for reporting this issue! Interesting, this would mean we would need to create some sort of kioskctl. However, currently you could do something like: ``` kubectl get spaces...

@cortex93 thanks for clarifying! As I understand it correctly, you want us to implement support for spaces in `kubens`? While I agree this would be a nice addition to kubens,...