nebari-dev / nebari-dev/llm-serving-pack
Push container images to quay.io in addition to GHCR
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 3
- Avg merge
- 16h 31m
- Merged PRs (30d)
- 11
Description
Currently the CI workflow pushes operator and key-manager images only to GHCR (ghcr.io/nebari-dev/nebari-llm-serving-pack/{operator,key-manager}).
Add quay.io as an additional registry to match the pattern used by other nebari images (e.g. quay.io/nebari/nebari-operator).
This would involve:
- Adding quay.io credentials as repository secrets
- Adding a second login/push step in the build-images workflow
- Updating default image repositories in values.yaml to use quay.io
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
Start with the build-images workflow and values.yaml, then compare the registry setup with other Nebari image workflows. Add the repository secrets and Quay login/push configuration, update the default image repositories, and verify that the workflow configuration and resulting image references cover both operator and key-manager images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100