Worker authentication
When you connect GitHub repositories (Settings → Git), r5d provides that GitHub credential to connected macOS and Linux workers. It can be any GitHub account, whichever way you sign in to r5d. The worker configures Docker and containers-auth credentials and providesGH_TOKEN for the GitHub CLI, along with registry
and namespace metadata such as R5D_GHCR_REGISTRY and R5D_GHCR_NAMESPACE.
With Docker installed on the worker, you can build and push an image:
Authenticate your deployment destination
Your deployment destination needs its own access to private images. For Kubernetes, configure a namespaced image-pull secret or the registry integration supported by your cluster provider, and reference it from the workload. For Docker or another host, configure its registry login using the service account and credential mechanism you choose. You own the destination’s credential lifecycle. r5d does not automatically install or rotate credentials in arbitrary clusters, hosts, or services.GitHub Actions
Publishing an image and authenticating a deployment are separate steps. A workflow may publish to GHCR with aGITHUB_TOKEN that has packages: write. After publishing, authenticate to your destination using its supported workload
identity or secret mechanism, then deploy an immutable image reference.
Choose CI actions and permissions appropriate to your deployment destination.