-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delayed freight discovery #2544
Comments
Looking at this a bit more, I do see the following in the api pod logs, specifically when a manual refresh is triggered.
Figured it was a resource limitation, but the controller seems to use as much memory as I give it. It was at 2Gi when I opened this, currently at 10Gi. The interval refreshes seem a lot more consistent with more memory, but the above error happens any time a manual refresh is triggered. Once a manual refresh is triggered, I sometimes observe that interval refreshes stop working as well until I manually remove the refresh annotation. |
How many tags in total are there in the targeted image repository? |
Largest is about 1100 total tags, ~60 match the filter. ~1500 images total, some untagged, but policies keep it around this number pretty consistently. Find that it happens for projects whose warehouses have a very small number of tags as well though |
Those API server logs do not appear related to this in any way. They look to me like the UI's client disconnecting abruptly. |
I've updated image retention. Max tags in any repo kargo uses is now 500 with around 30 matching in any repo, but issue persists. |
Checklist
kargo version
.Description
Frequently I've found that new image tags will be available that match the specified warehouse configuration, but they will not be discovered in a timely manor. The warehouse is configured with spec.interval of 2m0s, but with debug logs enabled, I see the warehouse reconcile loop happens far less frequently, but its often random. Clicking the refresh button also does not seem to reliably trigger the check for new artifacts.
Steps to Reproduce
interval
refresh
on the warehouse, confirm the annotation is added with updated tsinterval
of clicking refreshVersion
Logs
The text was updated successfully, but these errors were encountered: