You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2021. It is now read-only.
CUE is another meta-configuration language that attacks the same problem set as Jsonnet. It provides a different set of abstractions that may make it more suitable for some deployments and team workflows. Would it be possible for kubecfg to implement support for CUE?
The text was updated successfully, but these errors were encountered:
I'm also very excited about cuelang. I wonder if kubecfg is needed in that world though. Doesn't cue already support integrating with kubectl? Kubectl now also supports diffs.
Doesn't cue already support integrating with kubectl? Kubectl now also supports diffs.
it does via its command -> tasks constructs (i.e. supports running any CLI really), but still wouldn't match kubecfg from interacting with the API itself iiuc, also kubecfg rather "liberal" multi-object structs handling (either single obj, lists, maps)
@mkmik I'm investigating kubecfg for these two, very impressive, features:
Best-effort sorts objects before updating, so that dependencies are pushed to the server before objects that refer to them.
Optional "garbage collection" of objects removed from config (see --gc-tag).
I'm not as familiar as I should be with kubectl and it's roadmap but from an outsider's perspective (someone who is relatively new to kubernetes tooling) it seems like kubecfg is much further along.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CUE is another meta-configuration language that attacks the same problem set as Jsonnet. It provides a different set of abstractions that may make it more suitable for some deployments and team workflows. Would it be possible for
kubecfg
to implement support for CUE?The text was updated successfully, but these errors were encountered: