stonezdj(Daojun Zhang)
stonezdj(Daojun Zhang)
After discussion, we decided to implement it in this way 1. Add a configuration “Skip Scanner Pull Update”, if Harbor admin checks it, the scanner will not update the pull...
> We also facing this issue in v2.6.1 Please specify the container images that fails to pull by proxy cache?
Summary of this issue: the image tag is not guaranteed to be cached in Harbor, because it depends on the docker client's behavior, if the tag/digest information is cached local,...
Did you use the harbor-helm? It seems the env PERMITTED_REGISTRY_TYPES_FOR_PROXY_CACHE helm chart is out of date
If you are storing helm charts as OCI artifacts. tag immutable feature should work whatever it is a container image or helm chart.
The source of firstfloor/before_reindex:latest: https://github.com/stonezdj/before_reindex
Because this issue is uneasy to reproduce in our env, and we have no clear conclusion for it, handle it case by case.
The issue might related to the glibc2.28 change. the glibc 2.28 changed some character sort order esp -_$ with a-z A-Z see https://wiki.postgresql.org/wiki/Locale_data_changes https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade.html It caused the database index corruption....
Actually the GC job is still running in job service, but you have to get the job id and check the logs in the file system. maybe this feature could...
It is the same to logs in DB.