Detect and surface newer Helm chart versions on ClusterSummary - #772
Merged
gianlucam76 merged 1 commit intoJul 20, 2026
Merged
Conversation
Sveltos now checks, on a periodic background pass, whether a deployed Helm chart (sourced from an HTTP repository or OCI registry) has a newer version published upstream. Separately, whether a newer patch release exists within the same major/minor line. This is detection only: chartVersion in the ClusterProfile/Profile is never touched automatically; if you want to move to a newer version you still update it yourself. The result is reported directly on the ClusterSummary that owns the release, alongside the chart identity Sveltos already resolved at deploy time (chartName, repositoryName, repoURL).So it's visible per cluster. latestVersion/latestPatchVersion are only ever populated when something genuinely newer exists; lastCheckedTime advances on every successful check regardless of outcome, so a chart that's confirmed up to date is distinguishable from one that simply hasn't been checked yet. If a chart gets redeployed to a newer version between periodic checks, any stale "you're behind" info from before that deploy is cleared immediately rather than waiting up to a full check interval to self-correct.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sveltos now checks, on a periodic background pass, whether a deployed Helm chart (sourced from an HTTP repository or OCI registry) has a newer version published upstream. Separately, whether a newer patch release exists within the same major/minor line. This is detection only: chartVersion in the ClusterProfile/Profile is never touched automatically; if you want to move to a newer version you still update it yourself.
The result is reported directly on the ClusterSummary that owns the release, alongside the chart identity Sveltos already resolved at deploy time (chartName, repositoryName, repoURL).So it's visible per cluster. latestVersion/latestPatchVersion are only ever populated when something genuinely newer exists; lastCheckedTime advances on every successful check regardless of outcome, so a chart that's confirmed up to date is distinguishable from one that simply hasn't been checked yet.
If a chart gets redeployed to a newer version between periodic checks, any stale "you're behind" info from before that deploy is cleared immediately rather than waiting up to a full check interval to self-correct.