Brian Grant

@johnbelamaric Deployment and ReplicaSet. Job and Pods.

Enumerating all the revisions in one resource is a scalability problem and violates Kubernetes API conventions. Anyone who wants to see the revisions can list the revisions separately.

Package would create and manage PackageRevisions. How we would implement deletion is an interesting question. There are multiple options, including asynchronous GC. The whole reason for aggregated APIs in general...

On creating a new package: It's a good point that we have at least two ways of creating new packages currently, init and get: https://github.com/GoogleContainerTools/kpt/blob/main/docs/design-docs/07-package-orchestration.md#package-authoring

An example of an application with lots of configuration is kafka: https://github.com/bitnami/charts/blob/master/bitnami/kafka/values.yaml#L93 https://github.com/mesosphere/dcos-kafka-service/blob/master/frameworks/kafka/universe/config.json Similar to the overall approach to WYSIWYG configuration, I wouldn't want to abstract the application configuration. For...

With #3118, we wouldn't technically need a custom source/sink. We'd still need custom parsing, marshaling, and visualization, though.

As a concrete example that would address a segment of applications, we looked at Spring Boot config (application.properties) in the early days of the kpt project, but it looks like...

One specific category of application configuration is resource-dependent configuration: VM heap size, thread pool sizes, simultaneous connections, cache sizes, etc. Network- and disk-intensive applications often have a number of these...

This video discusses an in-pod templating approach using init containers, which is a variation on the entrypoint.sh script approach: https://youtu.be/eJmNSYvelSw?t=1087 I'm liking the Augeas idea, though. If we could convert...

https://osquery.io/ apparently integrates with Augeas. https://www.uptycs.com/blog/using-augeas-with-osquery-how-to-access-configuration-files-from-hundreds-of-applications That's read-only, for queries. Puppet integrates it also, for setting values: https://puppet.com/docs/puppet/5.5/resources_augeas.html And there's Go integration: https://dev.to/raphink/configuration-surgery-with-go-structure-tags-12a4