What scale is kapitan designed for

[th31nitiate]

It been a while since I have made use of kaptian. I always found it intriguing working with it because it provided intuitive interfaces to Jsonnet. This is generally a rare thing is the industry is still adopting Jsonnet as a whole.

My question is centered around what is the idealized method for adopting kapitan. I have heard people say that it's supposed to be utilized to package platforms. This is all well and good but this explanation lacks depth since it does not explain at what point to initialize the adoption of the tool. We can consider it as next generation configuration management with a focus on parameters. Though when should it be adopting into a project. Let us assume that most people already have tools their accustomed to in their own environments, let alone introducing something new require further learning.

I've always considered it useful for developing infrastructure from the ground up or as a wrapper, for managing existing infrastructure's parameters. The later work's because we use shell scripts to integrate it with any tool's while generating configuration file's, we can use it with complex ansible playbooks.

I would also be intrigued in better understanding how it can be useful to solo developers or for a better term "contractor's" who may not be using Kubernetes from the get go. I can comprehend it's usefulness in CI/CD processes and the like. It a modular system which is adaptable to various scenarios provided a little curiosity & creativity.

Im just wondering other peoples thoughts regarding this ?