Repository navigation
Conversation
…main charts/mainloop renders what k8s/apps/mainloop/base and its overlays did, with the deployment-specific parts (strategy, resources, site config, control-plane auth, database, commands) as values. CI packages it as oci://ghcr.io/oldsj/charts/mainloop 0.1.<run number> with the commit's image digests pinned. Kind and the live dev instance now install the chart. The live instance's values and dev kagent agents come from MAINLOOP_DEV_CONFIG and its kube context from DEV_LIVE_CONTEXT, so neither lives here; ci/live-dev-values.yaml is a generic example. The kind and dev-live overlays are gone. The prod overlay, devloop and the release job stay until production moves to the chart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
charts/mainloop: a Helm chart rendering whatk8s/apps/mainloop/baseplus the overlays did. Deployment-specific parts are values: strategy, resources, site config, control-plane auth, database (CNPG or local), and the dev commands.images.yml, newchartjob): on each push tomain, CI packages the chart asoci://ghcr.io/oldsj/charts/mainloopversion0.1.<run number>, appVersion<sha7>, with that commit's image digests pinned. Run numbers only grow, so a late or re-run job never outranks a newer chart.make kind-up/make dev) installs the chart withvalues-kind.yaml.make dev-live) installs the chart.*-devkagent agents come from$MAINLOOP_DEV_CONFIG, and its kube context from$DEV_LIVE_CONTEXT, either from the environment or from.env.ci/live-dev-values.yamlandci/production-values.yamlare generic examples usingexample.test.overlays/kindandoverlays/dev-live.overlays/prod,devloopand thereleasejob. A follow-up removes them.Verification
server/internal/deploytestwas ported tohelm template(59 subtests passing).checksum/configannotation that replaces the manualconfig-revision.helm lintis clean, and the packaging steps were dry-run locally.make dev/make dev-livethrough DevSpace (DevSpace isn't installed on the machine I worked on).helm upgrade --take-ownershipto adopt the objects kubectl created earlier. That needs Helm ≥ 3.17.After merge
chartrun creates thecharts/mainlooppackage as private. Make it public once in its package settings, as withcharts/opencozy, so Argo can pull it without credentials.MAINLOOP_DEV_CONFIGandDEV_LIVE_CONTEXTbefore the nextmake dev-live.Follow-ups (not in this PR)
VITE_API_URL=https://mainloop-api.olds.network(inimages.ymland the README).docs/specs/warm-state.mdhas historical run notes naming personal hosts.🤖 Generated with Claude Code