Scott Andrews

Have you considered creating an [Octant plugin](https://octant.dev)? We recently created a [plugin for Knative](https://github.com/vmware-tanzu/octant-plugin-for-knative).

> @tomkennedy513 / @matthewmcnew this will have quite a bit of an adverse effect on the resource utilization of the final build pod. Currently the resource utilization is calculated by...

Based on the current behavior, it seems that the gradle and maven buildpacks are mutually exclusive. Should they be moved into independent groups and made non-optional within the respective group?...

@renuy I didn't see that config sample. I probably used the table of contents on the page to skip the overview section and go directly to the `ownershipLabelRules` section.

Is this something that needs to be configurable, or configured once? The only client for the webhook is the k8s api server, so as long as that client is compatible,...

Cartographer v0.4.0 does not work on k8s 1.24 for the issue you called out. Try using [Cartographer v0.5.0](https://github.com/vmware-tanzu/cartographer/releases/tag/v0.5.0). The cartographer.sh website should be updated to use v0.5.0 as the default....

If you can avoid it, it's best not to inform with a cache on Secrets and instead look them up as needed. ServiceAccount are probably still ok as each resource...

Looks to already be working.

@100mik yes, I'm aware of the exists annotation. Please read the issue. I'm trying to point out a deficiency in the current behavior as designed, not looking for a work...

Not blocking anything, I can get by with the exists annotation on a CRD. Just calling out the design gap.