John Belamaric

Yes, exactly. The Porch system is in a management cluster and the workloads run in other clusters and are configured with their workloads via ConfigSync. While it’s also possible to...

For 1) first, let me say that in general, yes, conceptually what you are saying can work. This does require though a component to read the "provisioner" status and write...

I would probably classify an eternally growing list as a bug rather than an enhancement. Eventually this will reach various limits and cause different parts of the pipeline to puke.

Natasha's proposal and Morten's follow up comments make sense to me. Should we also capture additional metadata about the draft - like who created it? I guess that's a separate...

In Porch (server side), revisions will be created like this: - When creating a package from scratch, it starts at revision 1. - When cloning a package, say A to...

@henderiw this is all server side and automatic

I am not sure I understand the question completely. Yes, the client will decide what changes are needed to a package. But "client" here could be a controller - for...

Yeah, I see your point. As part of reconciliation, the controller needs to decide if the resulting package has changed after re-applying any inputs or transformations or whatever the controller...

> If the client wants to make this decision based on what would change in the cluster, it would be possible to leverage the `kpt alpha live plan` command, that...

> Is the suggestion that, if the porch sever sees a diff between the in-cluster KRM resources and the latest package revision, that the porch server will then automatically create...