Brian Grant

@delve I expect kpt to work with multiple levels of derivation, such as generic blueprint -> multi-environment app blueprint -> specific environment deployment package

We'll want a way to be able to set properties in common per environment across multiple applications -- mixins effectively.

Composing inputs with blueprints to create specialized deployment packages is covered by #3347. Orchestration of bulk changes is #3348.

A few scenarios to try: * Write application configuration from scratch for a specific application (bespoke and off the shelf) * Publish the configuration for an off-the-shelf application * Deploy...

Not that we're lacking for example applications to try, but here's another: https://github.com/GoogleCloudPlatform/bank-of-anthos It uses plain yaml, has a skaffold config, and has separate directories for prod and dev configs....

An example from slack: https://github.com/treactor/treactor-helm https://github.com/treactor/treactor-kpt https://github.com/treactor/treactor-kpt-functions

I took another look at the kubernetes dashboard, portainer, k8syaml.com, k8od.io, lens, monokle, octant, the GKE UI, the Ambassador Labs clickops experience, and [Humanitec](https://docs.humanitec.com/reference/concepts/app-config). If starting from scratch, starting with...

I thought about just optimizing for starting blueprints from blueprints, but that would create a chicken and egg scenario of how to create base blueprints. We could potentially provide some,...

The GKE Deploy experience starts with the container image, which it can autocomplete from GCR or AR. It allows, but doesn't require, specification of the entry point and inline env...

Some projects have embraced the struct-constructor approach. gimlet.io builds a UI on top of this chart (and any chart with jsonschema for the values): https://github.com/gimlet-io/onechart/tree/master/charts/onechart/templates https://gimlet.io/concepts/onechart-concepts/ The UI can support...