This is overall a bad idea, and I wouldn't touch the clusters i managed with a ten-foot pole.
For starters, having nothing running in the clusters means you have to give rw cluster access to developers. Developers should not be allowed near production without adult supervision.
Then, it simplifies nothing but adds its own complexity on top. You still need to understand helm for when this tool will (inevitably!) produce something that doesn't work the way you thought it would or when it produces something that doesn't match the mental model you made about it.
Also it seems to also spin local kubernetes clusters?
Also it seems to be have a dependency on nip.io hard-coded? Looks like an easy jackpot kind of target ? (you hijack nip.io dns records, you get a bunch of traffic from developers' laptop).
For starters, having nothing running in the clusters means you have to give rw cluster access to developers. Developers should not be allowed near production without adult supervision.
Then, it simplifies nothing but adds its own complexity on top. You still need to understand helm for when this tool will (inevitably!) produce something that doesn't work the way you thought it would or when it produces something that doesn't match the mental model you made about it.
Also it seems to also spin local kubernetes clusters?
Also it seems to be have a dependency on nip.io hard-coded? Looks like an easy jackpot kind of target ? (you hijack nip.io dns records, you get a bunch of traffic from developers' laptop).
So a bad idea overall in my opinion.