Ability to group resources from `k8s_yaml`

[designermonkey]

Describe the Feature You Want

I understand that this is primarily for developing resources locally, but it would be great to be able to properly group resources by namespace. so that in the UI we can see all the resources (like Ingress, Service etc) alongside the Pod, Deployment etc. This would make it so easy to re-apply an entire namespace.

Current Behavior

I don't feel the automatic naming thing is working well, as it names things like resource-name:type rather than using the actual namespace of the resource.

Why Do You Want This?

For example, cert-manager is applied as multiplt separate resources, which are all separate running containers, but any other k8s config like Services are all lumped under uncategorized which makes it hard to restart all of cert-manager on it's own.

[nicks]

Here's a doc on how to group resources: https://docs.tilt.dev/tiltfile_concepts.html#configuring-kubernetes-resources

[designermonkey]

While I appreciate the link to a document I already read, my question is a little more nuanced than that.

As you can see I wrote that the naming convention isn't helpful in that it doesn't use the namespace first, meaning I have to know all the names of all resources in advance to be able to group them. So using cert-manager as an example, I want to be able to easily group all the differently named resources in the UI. I simply can't do that at present.

[nicks]

ha, it's not personal! like 50% of the life of an OSS maintainer is DMs where they just need a link to docs.

i'm not totally sure what solution you're asking for though.

For the specific example you gave, cert-manager, we usually encourage people to use Helm - https://docs.tilt.dev/helm.html#installing-existing-charts. The helm package behavior is usually more what people want for a discrete set of resources like cert-manager.

[sztyup]

@nicks My situation is similar, I have lots of resources (for example mariadb-operator users,grants, etc) which are frequently added, deleted, renamed and always keeping them up-to-date in Tiltfile is error prone and adds extra work that is not productive. I think the best solution would be the ability to group resources based on labels/annotations. Do you think that is reasonable? I might be able to try to work on a PR if you point me in the right direction.