Repository navigation
fix(platform): render a lab-registry component chart through its host port - #511
Merged
Merged
Conversation
This was referenced Oct 10, 2026
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.
Problem
agentlab platformcould not install a component chart pushed into the lab registry. An overlay withcomponents.<name>.repository: oci://<cluster>-registry:5000/chartsandinsecure: truestopped at "Side-loading the platform images". The host-side render of the component chart tried to resolve<cluster>-registrywith the host's DNS, and only the kind network knows that name. No repository value worked for both the host render and Flux.Proposed solution
localhost:<platform.devRegistryPort>) over plain HTTP. The connectivity chart of achartPathlab is pushed through the same address. The HelmRelease keeps the kind-network URL, which source-controller can reach. The boot log names both addresses.spec.insecurenow reaches the host render as plain HTTP, for the tag listing and the chart pull alike.docs/platform.mdgains a section, "An unreleased component chart", with the push and the overlay.Acceptance criteria
components.kagentatoci://<cluster>-registry:5000/chartswithinsecure: trueinstalls withagentlab platform, its HelmRelease Ready and platform-test green (lab proof below).spec.insecure, the plain-HTTP render and tag list, and the refusal wording.Proof (agentlab, this branch's binary)
helm push … oci://localhost:5001/charts --plain-http(digestsha256:aca6c5e4…). Overlay:components.kagent.repository: oci://agentlab-registry:5000/charts,insecure: true,versionRange: "1.7.0".agentlab platform: exit 0,rendered 17 of 17 component charts.kagent:oci://agentlab-registry:5000/charts/kagent,insecure=true, artifact1.7.0@sha256:aca6c5e4…. HelmReleasekagent: Ready=True,history[0].ociDigestis the pushed digest.agentlab platform-test: exit 0, all PASS.agentlab platformre-run: kagent back on the gsoci chart 1.7.0 (sha256:02f633a3…), Ready.Closes #509
Written by an agent.