actions / actions/runner-container-hooks
Set Default Docker registry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 112
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Hi @nikola-jokic and team,
I am using the Runner scaleset with kubernetes mode and ran into an issue when using 3rd party GitHub Actions that are Docker based. We have kyverno policies that prevent any pod from getting scheduled if the image registry used by the pod is not pointing to our Artifactory instance. Is there a way to set an override value to ensure all Docker based based actions will be using the registry to pull the image from?
Thanks for all the awesome work,
Shankar.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Runner scalesets in Kubernetes mode, third-party Docker-based actions, and Kyverno policies, but no files, tests, or entry points. Start by identifying how Kubernetes-mode actions select image registries; define the supported Artifactory override and verify that all Docker-based action images use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, kubernetes, typescript
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100