John Belamaric

The plan for this in Nephio right now (which is to say, "very early") is that targeting is done by targeting per cluster repositories, with separate packages for the workloads...

There are certain common operations that you may want to do on an application deployment but not build into the base blueprint. For example, creating a PodDisruptionBudget or HPA. It...

Just to gather things in one place, a couple other examples for package dependencies: 1) Cloud provider SAs, KSAs, and associated workload identity setup (see https://github.com/GoogleContainerTools/kpt/pull/3388#discussion_r925126665) 2) Cluster Proportional Autoscaler...

> There are certain common operations that you may want to do on an application deployment but not build into the base blueprint. For example, creating a PodDisruptionBudget or HPA....

Deployment of packages across cloud providers is another common thing we may want to see if we can help with. In some cases, this can be handled with separate packages...

> We'll also want the UI guidance for creating and editing deployments to be different than for creating a blueprint. I would go so far as to say that the...

> Serious question: In the consumption-oriented UX, what is the delightful "wow" experience we'd be aiming for, compared to a UI form for entering helm chart values? > I think...

As we discussed earlier, it probably should block Proposing - but allow the cloning and saving. So it has to stay a Draft until it passes all validators.

> And yes, each update of a package will be like doing an update on the individual package, so they will all get the additional update task. The controller should...

I agree it makes sense to move away from a single leader. I do not, however, think a completely flat structure will work well for us. The primary reason being...