- Need a window of 3 days of engineering time to make changes for move and address issues that pop up with upstream/downstream builds and CI
- Propose to wait till after 1.0.1 release, prior to 1.1.0
- Move repositories identified below from github.com/fusor to github.com/konveyor
- Note, only the specified repositories from github.com/fusor will be moved, 'fusor' org has many unrelated repositories we will not move
- Update the golang sources for package references to refer to 'konveyor' instead of 'fusor'
- For Migration controller/operator/UI
- For CPMA
- Setup image builds to publish to https://quay.io/konveyor/
- Update example depolyment scripts to reference https://quay.io/konveyor/ for images
- Update upstream CSV examples to reference https://quay.io/konveyor/
- Update CI for github.com/konveyor changes (T.B.D)
- Update CI to test images to https://quay.io/konveyor/ (T.B.D)
- Verify mig-agnosticd/agnosticd deployments work, likely need to tweak some paths in agnosticd such as:
- Prepare a downstream build for 1.1.0 with latest source
- https://github.com/fusor/mig-operator
- https://github.com/fusor/mig-ui
- https://github.com/fusor/mig-controller
Forked velero repos are only for handling short-term early patches/builds before getting into upstream. We intend to contribute/follow upstream Velero and have no desires to deviate in long-term
- https://github.com/fusor/velero
- https://github.com/fusor/velero-plugin-for-microsoft-azure
- https://github.com/fusor/velero-plugin-for-gcp
- https://github.com/fusor/velero-plugin-for-aws
Forked restic repos are only for handling short-term early patches/builds before getting into upstream.
- Ansible automation for deploying clusters to AWS
- https://github.com/fusor/migpvbenchmarks
- https://github.com/fusor/mig-demo-apps
- Overview Page to describe project and repositories