Anthony Yeh

@danisla Although you may observe the order of map fields changing in the `last-applied-configuration` annotation over time, the way we check diffs to see if an update is required should...

@mikefaraponov wrote: > So, new api will looks like configuration file per statefulset of metacontroller? Yes. Also with the option to keep controller configs in multiple files and specify them...

@willnewby wrote: > As long as controllers are represented in a way that's still easy-to-understand (despite the CRDs seemingly going away) The current plan is to keep the configuration format...

@luisdavim Do you mean it's important that informers are shared across all metacontroller-hosted controllers installed by any user? Or would it be enough that all of your own controllers share...

I think it would be reasonable to add the ability to define static headers in the Webhook config spec. It may not be secure enough though since anyone who could...

I have thought about those, but I don't think they would have much in common with Metacontroller other than the general principle of offering limited, declarative interfaces as an alternative...

The last time this came up, I think the problem was that newer versions of Kubernetes started setting metadata.generation on CRD objects, even if the CRD's status subresource is disabled....

Yeah that matches what I was imagining. Essentially we'd have an in-memory cache of `customize` hook responses (if the hook is defined) that gets invalidated whenever the parent spec changes....

As a suggestion for prototyping: semantically we want this to be exactly like if we called the `customize` hook every time just before we call `sync`. You can prototype the...

It sounds like you want to make controllers that only act within certain namespaces, and you want Metacontroller to enforce that restriction instead of relying on the hook code to...