Repository navigation
Conversation
…#95) Drops GHCR entirely rather than dual-pushing, per explicit preference to avoid any GitHub-hosted-registry dependency for the pull side - the existing in-cluster ghcr-secret credential had already silently expired, leaving frontend and the data-pipeline CronJob in ImagePullBackOff for over 3 weeks. Harbor's push robot (robot$oss-dev-analytics+push) replaces the GITHUB_TOKEN-based ghcr.io login. Also captures the pushed digest in the job summary and adds workflow_dispatch so a build can be triggered on demand. Requires HARBOR_USERNAME/HARBOR_PASSWORD repo secrets (added separately, not committed here). Co-Authored-By: HuntC19 <137342864+HuntC19@users.noreply.github.com> Co-Authored-By: mikeybud08 <mikeybud08@users.noreply.github.com> Co-Authored-By: Claude Sonnet 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.
Part of oss-slu/oss_infra_ops#95.
Replaces the
ghcr.iologin/push in bothbackend.ymlandfrontend.ymlwithregistry.oss-slu.online(the self-hosted Harbor instance from #92). Drops GHCR entirely rather than dual-pushing, to avoid continuing to depend on a GitHub-hosted registry for the pull side - worth knowing: the in-clusterghcr-secretcredential had already silently expired, leavingfrontendand thedata-pipelineCronJob stuck inImagePullBackOffin the cluster for 3+ weeks before this PR. This migration fixes that as a side effect, once merged and deployed.Needs two repo secrets added before this can run (Settings → Secrets and variables → Actions):
HARBOR_USERNAME:robot$oss-dev-analytics+pushHARBOR_PASSWORD: (Harbor robot secret - see the infra PR/chat, not pasted here)Also adds
workflow_dispatchto both workflows so a build can be triggered on demand without needing a real code change, and writes the pushed image digest to the job summary (needed for the next step: pinningk8s-manifests/oss-dev-analyticsto an immutable digest).🤖 Generated with Claude Code