Level2 Guide - Githubissues

Write a doc showing how to expose a service. If the quickstart is level 1, this is the next level 2.

Make it readable without having to apply any changes like the Quickstart.

Make k3d + mkcert optional as a separate page. Out of scope. Management clusters, secret syncing, auth proxy, monitoring.

Key Concepts

Focus on the key concepts of the tool, not the thing the tool is building.

[ ] CUE files are organized into a tree.
[ ] The root and leaves are the most important.
[ ] Each leaf produces a BuildPlan
[ ] A BuildPlan contains a list of zero or more components
[ ] The kinds of component are Helm, Kustomize, Kubernetes
[ ] Spend some time talking about how Kustomize is equivalent to kustomize build against the directory, which requires a kustomization.yaml that lists the rest of the files.
[ ] Mention Kustomize can be used to integrate plain old yaml files including those that come from kubectl get -o yaml
[ ] Data is only visible further out along a branch. This means data defined at one leaf is not visible from another leaf.
[ ] Data shared by multiple components must be defined closer to the root. For example, #Namespaces.
[ ] The components and platform directory are conventions, not hard requirements.

Level 3

[ ] Mention we can import a yaml file to CUE to get strong type checking.
[ ] Show what a build plan looks like. cue export -out yaml ./components/namespaces