Hi @stno_9153 , Oh yeah, that'll make a HUGE difference for public repositories. OTherwise it'll probably not work at all :) Anyway glad it's working now Thanks, Alana

Hi @brandon_owensby_2976, Argo CD is free / open source and no license is required. You'd be better off learning that than trying to do Kubernetes another way. FYI there's also Kargo, which is a "wrapper" that sits on top of ArgoCD and has some kind of promotion workflow outside of typical GitOps (pull requests I guess?). To be honest, I really don't know if the Kubernetes extension even works; it was originally intended for Otter, to create a "Desired state" and offer an alternative to Git-based approaches. But there's just no demand and GitOps is just the Kubeernetes standard. We haven't tested it in years. We do not plan on migrating it to the next SDK version. It's just a light wrapper around kubectrl, which has probably changed over the years. If you really wanna mess with Kubernetes outside of Argo CD I would just run kubectrl apply/replace directly. Good luck!!

Hi @christian-georg_5533 , Thanks for sharing the additional context, that makes sense. You are correct -- ProGet is a package repository with SCA as a value-added feature. Most of our users create SBOM because they are required to due to regulations, and but don't find much use outside of that :) Of course we're always interested in expanding features but we aren't really striving for the "central SBOM Repository" use case now. We'll see if there's more demand down the line, feel free to share more information (other products, tools) sinc eit's always good to think about future versions of the product! Cheers, Alana

Hi @parthu-reddy , This does not appear to be a "fat manifest". Two other things are coming to mind. First, are these referenced in any helm charts? If so, they won't get removed unless you delete the helm chart first. Second, how about trying a separate policy, "Delete untagged manifests"? That should clear out these images. Thanks, Alana

Hi @cole-brand_2889 , Wow, I didn't realize that S3 rate-limited like that!! That's good to know. Unless this is something that could be configured as an advanced SDK switch in the S3FileSystem, then I don't think there's much that could/should be done in the ProGet or extension code. After searching the error (and seeing this very post on the first page of Google ), this just seems to be endemic with S3; there's no published rate limit, and even in AWS official blog article the only solutions seem to be "follow the error message and reduce your request rate". There's probably something you can do do on the load-balancer side of things... reducing concurrent requests, etc. Let us know what you find! Thanks, Alana

Hi @davidroberts63 , While connector filters were never really designed to replace the "approved packages" workflow, we've seen many users do exactly that over the years, yielding hundreds of entries. It's not exactly a use case we recommend, as one of the big benefits of the approved packages flow is to prevent "instinctively upgrading dependencies" yielding in regressions. But, if you're already effectively doing that through automation, then I suppose you already know the risks :) From a performance standpoint, it shouldn't make a notable impact. Those have been optimized for quite some time now. Thanks, Alana

@atripp Thank you for your help. This resolves my problem. Good to hear that it will be default behaviour, current behaviour is not intuitive.

I actually haven't looked into pgutil yet. I'll check it out. But overall, ProGet does a pretty good job. Right now, I really can't think of anything that ProGet can solve uniquely.

No problem; I will use the generic one :) @george-bowen_9415: Did you experience delays in V5, and do you have any significant amount of group memberships? :) -Sigurd

Thank you very much.

Hi @parthu-reddy , Thanks for the additional information. Thinking about it further, I suspect this was a temporary network outage. It could have been DNS related, or who knows what. As for your configuration... 5000 is definitely too high; set this towards 100-500 max. If you're working on a load-balanced cluster, this should be done at the load balancer instead. I was incorrect about api.nuget.org, that is also used by the V3 API. I thought it was only V2. So please disregard. It's unlikely metadata caching will help, but you could try it. That's a relatively short-lived cache meant for traffic bursts, and it's not really going to help with a network outage. -- Dean

@rcpa0 thanks for letting us know; we'll try to fix this next time we make some changes to pgutil it should only print "Version is not a valid semantic version." or something

Perfect, thanks Alana :)

Hi @davi-morris_9177 , I'm afraid this behavior is expected because kotlin-stdlib-2.3.20.jar is not in the downloaded index file. There's is no file-listing API, which means there's no way to know what should be there otherwise. The Maven client downloads "blindly downloads" some files, and "silently accepts" a 404 for other files. When it's downloaded (cached), then ProGet knows about it. So, you really need to download the artifacts first if you want to make a curated feed I'm afraid. -- Dean

Thanks Alana, that is fair. I am mainly wanting to make sure that the app remains supported regardless of whether I deploy it on Linux using docker, or on a kubernetes platform. It is assumed there is underlying platform support that will be on us.

Great, thank you!

Thanks for pointing that out @rcpa0 ! I've just updated the docs now.

Hi @devops-user @joshua-mitchell_8090 , Thank you so much for testing! We'll merge this in via PG-3251 in tomorrow's maintenance release. As for the other error, it's technically unrelated - but that package has such a long "compliance analysis report" that it's getting truncated in the database cache. PostgreSQL complains about that, SQL Server silently does it. Anyway w'ell fix via PG-3250 perhaps in tomorrow's release as well. Cheers, Alana

Hi @Stephen-Schaff , The Docker API does not use API keys but a ticket-based system (i.e. docker login). Here is how to use it: https://docs.inedo.com/docs/proget/docker/semantic-versioning#example-powershell-script-to-authenticate-to-docker We added some kind of support via PG-3206 in ProGet 2025.20, though it was only intended to address self-connectors to Docker registries. I do'nt know how well it will work here. Thanks, Alana