John Belamaric
John Belamaric
I am not sure this is the right approach. I can't think of other K8s resources off hand that have this sort of relationship. It makes sense to explore the...
> @johnbelamaric Deployment and ReplicaSet. Job and Pods. I don't really think of those as "containment" relationships, which is how I see this. Deployments create and manage ReplicaSets, and the...
I like an app-specific function, especially if is written in something like Starlark that does not require building and maintaining and coordinating versioning for a separate container image. An init...
I suspect all three will be needed, but from a preferred order, I find Option 3 more aligned with the vision, for a couple reasons: * I think apply-time transformations...
Agreed. What I missed in your description of 3 above was that we would store in the *canonical* format - I was reading it as representing the native format and...
The other point we need to consider is the source of truth. Clearly the generated ConfigMaps are not it. So it leaves the native and canonical formats. If we store...
#3422 is relevant to this discussion
I added a drawing above. We need to identify what options are available at each stage to modify config, and identify why any particular mutation should live in any particular...
cc @droot @mortent @justinsb @bgrant0607
> "Adaptation" sounds good to me +1 ok > We might want more specific terms for the case that a platform team takes a component configuration Possibly. The chains can...