Dmitriy Kalinin

> Expectation is that the secret doesn't appear to be visible immediately as the Kubernetes admission controller takes time to inject the credentials and certificate into the token secret it's...

my 2c: this use case seems pretty rare, i think its worth seeing how common this problem becomes/is before promoting this behavior to a default rule.

yeah, currently it needs something like this: ``` kapp app-group deploy --directory . -g group-name ``` looks like it is not checking for group name to be required. (fixed here:...

> another idea is to parse a CRD that doesn't get applied which defines the app's default group name. hmm, that's an interesting proposition. let me think on that during...

> But I'm seeing the first attempt to update that annotation is always a conflict (for which kapp retries) i think that's expected because deployments are annotated with revision annotation...

PR seems reasonable. it seems like there is a failing test.

kapp optimizes by default for as much parallelism as possible. since there was immediate relationship between resources being created and deleted kapp does not stagger them in any way. you...

> Yes I've been looking into the ordering possibilities already but I don't think they are applicable for this condition. can you explain why it's not applicable? people have used...

> Hence I don't see a possibilities to tie each resource with itself on replacement may be im getting confused here. when resource is changing (continue to have same name),...

we are considering adding two meta change-groups: change-groups.kapp.k14s.io/to-be-upserted and change-groups.kapp.k14s.io/to-be-deleted. additionally we are working on adding ability to add change rules via config, so this combination would be able to...