chore(plugindefinitions): increase helm chart and repository interval to 24hours#1908
Merged
abhijith-darshan merged 1 commit intomainfrom Apr 10, 2026
Merged
Conversation
IvoGoman
reviewed
Apr 10, 2026
Signed-off-by: abhijith-darshan <abhijith.ravindra@sap.com>
0dae5e2 to
666af37
Compare
IvoGoman
approved these changes
Apr 10, 2026
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
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.
Description
Increase HelmRepository and HelmChart interval to 24hrs.
HelmRepository .spec.internval is to periodical check the helm repository index (index.yaml)
This is not needed for OCI registries as there is no index.yaml
HelmChart .spec.interval is beneficial to periodically update the Helm chart when using version ranges or floating tags
ex
>=1.2.0orlatestIn greenhouse these are pinned versions of OCI references so both resource's interval can be set to a long interval such as 24hrs.
The versions are propagated via
(Cluster)PluginDefinition, so a change in version will trigger a reconcile on demand.What type of PR is this? (check all applicable)
Related Tickets & Documents
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist