Skip to content
This repository was archived by the owner on May 13, 2025. It is now read-only.
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

@mallardduck

Description

@mallardduck

Moving the follow up actions into this issue from the original PR.

  • Tag a v0.3.0 release here - which will release both images to GHCR
  • Add package/helm-project-operator label to existing issues in this repo
  • Shutdown usage of the helm-locker repo:
    • Move over the issues from helm-locker repo & label as package/helm-locker,
    • update helm-locker repo readme,
    • archive helm-locker repo, - created issue to track
  • [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-federator code 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.
  • [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-federator to use patched versions of this repo,
  • [n/a] subsequently ensure rancher-monitoring and rancher-project-monitoring are 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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions