Ideally in a way that does not require allowing certain fields, but simply uses everything.
Ie - in dev we take K8s config and -> compose (when using compose dev backend). In prod we basically pass the object as-is, with any additions (envars/etc).
Again, would remain all configured in a single kubetools.yml file (for now?).
Ideally in a way that does not require allowing certain fields, but simply uses everything.
Ie - in dev we take K8s config and -> compose (when using compose dev backend). In prod we basically pass the object as-is, with any additions (envars/etc).
Again, would remain all configured in a single
kubetools.ymlfile (for now?).