[dev-v2.9] rancher-monitoring 104.0.0-rc1 update #3835
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
Dependency updates for PushProx
Changelog
Problem
PushProx has out of date dependencies and has migrated to github actions which has modified the way docker manifests are published slightly.
There have been no functional changes to PushProx besides dependency upgrades.
Context
Rancher pushprox is used inside of rancher-monitoring to federate access to protected metric endpoints in a safe manner, such as control plane metrics and node-exporter metrics in RKE2 / K3s.
Testing
The testing should revolve around testing rancher-monitoring in RKE2 and K3s and making sure the core metrics show up in dashboards, as well as verifying dashboards for integrations such as
kube-state-metrics
Engineering Testing
Manual Testing
Tested pull-able docker images and helm template testing making sure the image tag has been properly updated
Automated Testing
PushProx CI.
QA Testing Considerations
linux/amd64
andlinux/arm64
setups for RKE2/K3s since docker manifests were modified slightly (verifying the images are pullable and run without issues on arm64 should be sufficient)Regressions Considerations
Backporting considerations