This repository was archived by the owner on May 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
This repository was archived by the owner on May 13, 2025. It is now read-only.
[Tech Debt] Follow up on helm-locker repo reorg #78
Copy link
Copy link
Closed
Description
Moving the follow up actions into this issue from the original PR.
- Tag a
v0.3.0release here - which will release both images to GHCR - Add
package/helm-project-operatorlabel to existing issues in this repo - Shutdown usage of the
helm-lockerrepo:- Move over the issues from
helm-lockerrepo & label aspackage/helm-locker, - update
helm-lockerrepo readme, - archive
helm-lockerrepo, - created issue to track
- Move over the issues from
- [n/a]
Implement new branching strategy (maybe after Alex PR merge, need to decide optimal order)- Realized this is getting ahead of ourselves since we want to merge this codebase into
prometheus-federatorcode base, - The goal to use new branching was slated for after that process completed and this was just the first half of that process.
- For now we will do minimal dependency bumps keeping Rancher 2.8 as our target; this should keep these projects more updated and maintain compatability with all necessary k8s versions.
- Realized this is getting ahead of ourselves since we want to merge this codebase into
- [n/a]
Rebuild Alex's PR to update helm-locker on this repo; will update both sets of dependencies at once.- I've realized a lot of the changes that happened since the PR was started supersede it,
- At this point I think we'll forego that PR (reevaluate later to decide if needed at all or if we close it),
- Update
prometheus-federatorto use patched versions of this repo, - [n/a] subsequently ensure
rancher-monitoringandrancher-project-monitoringare updated and in charts
This PR's n/a steps will be followed up on later in rancher/prometheus-federator#109 or other work in the prom-fed repo.