Add IsNamespaced Property to KubernetesEntityAttribute

[IvanJosipovic]

At the moment, it does not appear that there is a straightforward way to determine whether a given Kubernetes type is namespaced.

Having an IsNamespaced boolean property on the KubernetesEntityAttribute would be very helpful for consumers of the client library who need to programmatically distinguish between namespaced and cluster-wide resources.

This addition would simplify logic in tools and libraries built on top of the client and would not require access to the Discovery API.

Thanks for considering this enhancement.

[brendandburns]

I'm not certain if this information is in the open api specification, I guess it might be inferred from the path. We'd have to see what we have available at code generation time.

Is access to the discovery API a blocker? I think it is generally open to cluster readers.

[IvanJosipovic]

Is access to the discovery API a blocker? I think it is generally open to cluster readers.

I’ve just encountered a case where the Discovery API is not fully exposed. Despite the cluster running Kubernetes 1.31.0, the aggregation layer is disabled, and the discovery results only include a subset of resource types, even though our credentials have permissions to access many more.

Specifically, this is a SaaS platform that provides restricted Kube API access.

[tg123]

it is nice to have, lets add it

would you like to draft a pr or i will