New Repo Steps

[mallardduck]

Before/Upon move to rancher/ do

• 1. Request EIO create:
  • 1. GitHub rancher/kuberlr-kubectl repo,
  • 2. Docker Hub repo,
  • 3. Secrets for the GitHub to push to dockerhub
• 2. Find and replace mallardduck/rancher-kuberlr-kubectl to rancher/kuberlr-kubectl,
• 3. Find and replace mallardduck/rancher-kuberlr to flavio/kuberlr,
• 4. Find and replace rancher-kuberlr-kubectl to rancher/kuberlr-kubectl,
• 5. Find and replace rancher-kuberlr to flavio/kuberlr,
• 6. Update workflows to use EIO provided secrets
• 7. Add renovate (maybe it'll help catch docker tags used to build)
• 8. Review CIs and ensure all images and releases are published,
• 9. PR Shell to use the correct rancher/kuberlr-kubectl as the base for it.
• 10. Produce Shell POC image.
• 11. Complete RFC process and wait for review.
• 12. Update main branch to expected versions,
• 13. Create necessary older release branches and adjust to use proper kubectl versions,
• 14. Send PRs (or create issues) to rancher/charts to update any usage of rancher/kubectl and rancher/shell to use correct rancher/kuberlr-kubectl.

TODO

• The current main branch is for 2.9 since that's the primary dev target.
  • Upon rehoming to rancher we will:
    • - a release/v2 will be created with not changes needed;
    • - main can then be PR'd to use 2.10 target kubectls.
    • - release/v1 will be created and PR'd to match kubectl versions;

[mallardduck]

Renovate added here: #4

And it already caught 2 PRs for us; bumping kuberlr and GHA workflows

[mallardduck]

Note: During PR to main to add proper kubectl I found that k8s upstream stopped making builds for s390x so we dropped that.