4 ms·

> Koreo is the engine that powers Konfigurate, a batteries-included developer platform for startups and scaleups. Yaml is no go for me. Gradually typed langua

> Koreo is the engine that powers Konfigurate, a batteries-included developer platform for startups and scaleups. Yaml is no go for me. Gradually typed languages, with support of unkown values, like Nickel can be good.

dlahoda 2y ago
But if Kore starts where Kustomize ends (selectors like, inheritance like, binding like things) and covers 100% of Kustomize. But builds on top (i see CEL usage). I can be intresting to use this instead of Kustomize.
- dlahoda 2y ago
  twitter thread, > However, the two tools are not mutually exclusive. In some cases it can make sense to use Kustomize in combination with Koreo! Would be awesome Koreo make Kustomize no need. I feel insane getting into project where Helm, Kustomize and Koreo used at same time(they always do this). So if Koreo and Helm only, would be nice gradual step. One bad yaml with other bad yaml.
  - robertkluin 2y ago
    Honestly, Koreo can cover most of the use cases of the other tools just fine. We leverage Koreo to manage deployments of the Koreo controllers along with their service accounts and RBAC—it works quite well. We also use it with Helm in order to install, for example, ACK controllers which have existing Helm Charts. Our design is very, very deeply inspired by Kustomize. If Kustomize or kpt are sufficient, I would strongly encourage using one of them. We developed Koreo because we have cases where we need to sequence resource creation (for instance to map values from one resource to another) and wanted to programmatically set values.
- esafak 2y ago
  If we're going to ditch Kustomize, let's ditch it for something that isn't YAML, because Kustomize has the virtue of being established.
deleted 2y ago
[deleted]
mifydev 2y ago
I feel like I should just be able to generate k8s configs from Typescript with Typeconf if I add all the types there, is anyone interested in this?
- sudosteph 2y ago
  Yes. CDK has made me a fan of Typescript.
_joel 2y ago
Just get cdktf to manage the YAML, you may laugh but it's not so horrible as it sounds.

dlahoda 2y ago

But if Kore starts where Kustomize ends (selectors like, inheritance like, binding like things) and covers 100% of Kustomize. But builds on top (i see CEL usage). I can be intresting to use this instead of Kustomize.

dlahoda 2y ago
twitter thread, > However, the two tools are not mutually exclusive. In some cases it can make sense to use Kustomize in combination with Koreo! Would be awesome Koreo make Kustomize no need. I feel insane getting into project where Helm, Kustomize and Koreo used at same time(they always do this). So if Koreo and Helm only, would be nice gradual step. One bad yaml with other bad yaml.
- robertkluin 2y ago
  Honestly, Koreo can cover most of the use cases of the other tools just fine. We leverage Koreo to manage deployments of the Koreo controllers along with their service accounts and RBAC—it works quite well. We also use it with Helm in order to install, for example, ACK controllers which have existing Helm Charts. Our design is very, very deeply inspired by Kustomize. If Kustomize or kpt are sufficient, I would strongly encourage using one of them. We developed Koreo because we have cases where we need to sequence resource creation (for instance to map values from one resource to another) and wanted to programmatically set values.
esafak 2y ago
If we're going to ditch Kustomize, let's ditch it for something that isn't YAML, because Kustomize has the virtue of being established.

deleted 2y ago

[deleted]

mifydev 2y ago

I feel like I should just be able to generate k8s configs from Typescript with Typeconf if I add all the types there, is anyone interested in this?

sudosteph 2y ago
Yes. CDK has made me a fan of Typescript.

_joel 2y ago

Just get cdktf to manage the YAML, you may laugh but it's not so horrible as it sounds.