Repository navigation
chore: publish only the Arc chart from the MCR workflow - #1373
Merged
Merged
Conversation
Agent images are now built and published to MCR by a separate pipeline, with tags of the form <release tag>-<revision> (e.g. v0.18.16-1). Drop the image build, arch-specific publish and manifest bundling jobs, leaving the workflow to resolve the already-published tags and package the Arc chart. Tags are resolved from the MCR registry API by selecting the highest revision for a release tag. The chart is checked out at the plain release tag, since the revision suffix has no corresponding git tag. Point the Arc chart at the aks/v2/fleet repository path, where the new pipeline publishes, and add a README covering the publishing flow and the chart values whose behavior does not match their names. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
git describe reads tags from the checked-out repository, which a fork does not have: GitHub does not copy tags when forking, so the workflow failed with "fatal: No names found, cannot describe anything" on any fork. Read both release tags from the GitHub API instead, matching how the fleet-networking tag was already resolved, and fail with a clear message when a tag cannot be resolved rather than passing "null" downstream. The prepare-variables job no longer needs a checkout. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Britania Rodriguez Reyes (britaniar)
approved these changes
Oct 13, 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.
Description
Agent images are now built and published to MCR by a separate pipeline, with tags of the form
<release tag>-<revision>(e.g.v0.18.16-1). This removes the image-building responsibility frombuild-publish-mcr.yml, leaving it to resolve the already-published tags and package the Arc member cluster agents Helm chart.Workflow — dropped
publish-images-amd64,publish-images-arm64andcreate-image-manifest-bundle, leaving a singlepublish-arc-helm-chartjob.Tags are resolved from the public MCR registry API (
/v2/<repo>/tags/list) by selecting the highest revision for a release tag:RELEASE_TAG— fromaks/v2/fleet/member-agent, based on the latestAzure/fleettag (or thereleaseTaginput)FLEET_NETWORKING_VERSION— fromaks/v2/fleet/mcs-controller-manager, based on the latestAzure/fleet-networkingtag (or the newfleetNetworkingReleaseTaginput)The member agent, refresh token and CRD installer share a revision, as do the two networking images, so one lookup per family is sufficient. A missing image now fails the run with the available tags listed, rather than producing a chart that points at a nonexistent tag. Checkout uses the plain release tag, since the revision suffix has no corresponding git tag.
Chart — repointed to the
mcr.microsoft.com/aks/v2/fleetrepository path where the new pipeline publishes, with the test fixtures kept in sync. Added a README covering the publishing flow and the values whose behavior does not match their names. Added*_test.goto.helmignore, which was shippingcharts_test.goinside the published chart.Verification
Dry-ran the
prepare-variablesscript against live MCR:Packaged the chart with those values and confirmed all five rendered image references return HTTP 200 from MCR:
actionlintandgo test ./charts/member-agent-arc/...both pass.Notes for reviewers
0.18.16-1is a semver pre-release of0.18.16. This is safe for the Arc consumer: ClusterConfigDP persists only major/minor/patch and orders byc.MajorVersion desc, c.MinorVersion desc, c.PatchVersion desc, c._ts desc, so the revision sorts equal to the base tag and ties break on write time. It would not be safe forhelm search/helm install, which skip pre-releases without--devel.🤖 Generated with Claude Code