replicatedhq / replicatedhq/kURL
airgap kurl upgrades should only need to be run on one node
Open
Nobody has claimed this yet.
type::feature
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
Today, when updating a kurl cluster, there's a prompt to run a script to load images on the other nodes. While this works, this isn't a great experience, and can lead to issues if the script is not run.
It should be possible to bootstrap a registry and then rely on that instead of loading images local to every node.
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 by tracing the kURL cluster update flow and the script currently used to load images on other nodes. Investigate how an air-gapped registry could be bootstrapped during an upgrade, and consider the work complete when upgrades no longer require manually running that script on each node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100