Stefan Prodan

Have you've seen the controller reach 1Gi, are you sure the restart is due to OOM? From what you've posted here I see no evidence of OOM if the controller...

A Memory leak would always result in OOM, hence the issue title is confusing to me.

The extra memory you see can be reclaimed by the OS if it needs it, if you look at the memory dump you'll see this, there is no evidence of...

@AustinAbro321 please squash all commits into one and rebase force push.

@bigkevmcd this is good to go, please signoff all your commits and force push.

@bigkevmcd if you rebase with main, you'll find `runtime/cel` and the `InvalidCELExpressionReason`.

Hey @chanwit I suggest having the alpha and beta features behind feature flags. For beta you could enable those features by default but still allow cluster admins to disable them....

Are you using a RAM disk for the `/tmp` volume like showed here https://fluxcd.io/flux/installation/configuration/vertical-scaling/#enable-in-memory-kustomize-builds? Can you look in `/tmp` in kustomize-controller pod and see how large is it?

Ok so looks like all these problems are due to FS operations. The tmp should be empty almost all the time. Is there anything inside the repo that could cause...

I think first we should optimize the pulling, instead of downloading the whole artifact like we do here https://github.com/fluxcd/source-controller/blob/33dd859f72341d3da47b352e0aa4ce458edca6d8/internal/controller/ocirepository_controller.go#L458 We should get the manifest, and download only the selected layer.