Fix and modernize release workflows, complete ghcr.io migration, and parameterize jobs for easy fork usage#2363
Merged
ddelnano merged 6 commits intopixie-io:mainfrom Apr 27, 2026
Conversation
ddelnano
commented
Apr 27, 2026
| # Use the old style versions file instead of the new updates for the gcs manifest. | ||
| MANIFEST_UPDATES: "" | ||
| GOOGLE_APPLICATION_CREDENTIALS: ${{ steps.gcloud-creds.outputs.gcloud-creds }} | ||
| run: ./ci/update_artifact_manifest.sh |
Member
Author
There was a problem hiding this comment.
These docs are updated through a different workflow now.
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Improvements to operator and image release scripts that make builds idempotent and resilient to first-time runs against fresh registries Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Lets cloud/operator/vizier release builds push to a configurable container registry while preserving upstream's current gcr.io/pixie-oss/pixie-prod default. The registry can now be overridden via the IMAGE_REPO env var (set in workflow env from vars.IMAGE_REPO with a fallback). For operator, bundle_image and index_image now derive from image_repo so they track the same registry Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Lets release workflows be reused unchanged across forks. Buildbot identity (user.name/user.email) now reads from vars.BUILDBOT_NAME / vars.BUILDBOT_EMAIL with the existing pixie-io values as fallbacks. GH_REPO is now propagated from the workflow to cli/cloud build scripts (operator/vizier already passed it), so artifact_utils.sh no longer relies on a fork-specific default. The default chain falls through GITHUB_REPOSITORY (auto-set by Actions) before the pixie-io/pixie literal. Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
ddelnano
force-pushed
the
ddelnano/release-job-restructuring-and-fixes
branch
from
566701d to
9aba7f3
Compare
This was referenced Apr 27, 2026
vihangm
approved these changes
Apr 27, 2026
ddelnano
added a commit
that referenced
this pull request
Apr 27, 2026
Summary: Use github.repository for codecov upload target This complements the changes in #2363 to make the GitHub actions easily parameterized for any forks. Relevant Issues: N/A Type of change: /kind cleanup Test Plan: Reviewed this syntax against GH's documentation Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
k8sstormcenter-buildbot
pushed a commit
to k8sstormcenter/pixie
that referenced
this pull request
Apr 27, 2026
…parameterize jobs for easy fork usage (pixie-io#2363) Summary: Fix and modernize release workflows, complete ghcr.io migration, and parameterize jobs for easy fork usage Completes the ghcr.io migration started by earlier changes, repairs the bit-rot that accumulated since these workflows last ran, and parameterizes them via `vars.IMAGE_REPO` and `${{ github.repository }}` so forks can publish to their own registry without editing the workflows. Note: This change is best reviewed commit by commit. Relevant Issues: N/A Type of change: /kind cleanup Test Plan: Built vizier, operator, cli and cloud releases for the https://github.com/k8sstormcenter/pixie fork based off these changes * Ran a few pre-release builds that included an earlier version of these changes ([cloud-release](https://github.com/pixie-io/pixie/actions/runs/24548517833)) * Verify macos signing variable is set ``` $ gh variable --repo pixie-io/pixie get ENABLE_MACOS_SIGNING true ``` Changelog Message: Future cloud, operator and vizier release images will now pushed to ghcr.io/pixie-io instead of gcr.io --------- Signed-off-by: Dom Del Nano <ddelnano@gmail.com> GitOrigin-RevId: 44d42f1
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
2 participants
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.
Summary: Fix and modernize release workflows, complete ghcr.io migration, and parameterize jobs for easy fork usage
Completes the ghcr.io migration started by earlier changes, repairs the bit-rot that accumulated since these workflows last ran, and parameterizes them via
vars.IMAGE_REPOand${{ github.repository }}so forks can publish to their own registry without editing the workflows.Note: This change is best reviewed commit by commit.
Relevant Issues: N/A
Type of change: /kind cleanup
Test Plan: Built vizier, operator, cli and cloud releases for the https://github.com/k8sstormcenter/pixie fork based off these changes
Changelog Message: Future cloud, operator and vizier release images will now pushed to ghcr.io/pixie-io instead of gcr.io