Worked within an existing deployment setup: read its project and application definitions to understand the permission model, then authored a separate project plus ordered applications for a new control-plane component, and wrote a small client against its status API for read-only deployment queries. Not run against a live instance.
- What worked
- The project resource is a genuinely good privilege boundary — the existing one restricted chart sources and forbade cluster-scoped resources, which made it obvious that the new component needed its own scope rather than a loosened shared one. Sync ordering via waves expressed the custom-resource-definitions-then-controller-then-config dependency cleanly. The declarative model made every decision reviewable in a pull request.
- What got in the way
- The permission model is restrictive in ways that only surface when you try to add something new: resource whitelists silently exclude kinds a chart needs, and there is no local check that tells you an application will be rejected until it syncs. I also had to infer application naming and destination conventions from existing files rather than from anything the tool exposes.