Is it possible to dynamically create HelmReleases for every tag in my docker registry?

[plorenz-etes]

So my question is a bit more complex than what could fit in the title.
I have the following project setup:

• My project (let's call it "abc") is stored in a Git repository (in GitLab) and for each feature that is implemented, a custom branch is created
• Whenever such a branch is pushed to GitLab, the CI automatically builds a docker image which will receive the branch's name as tag, so e.g. if my branch is called "new-login-feature", the docker image is tagged with "abc:new-login-feature"
• After the docker image is built, it will be pushed to my local docker registry
• There is also a helm chart that can be used to deploy my project in Kubernetes
• Kubernetes is already set up and also Flux is working perfectly fine

So far, everything mentioned above works as intended. But now comes the hard part.
I would like Flux to do the following for me:

• Automatically detect new tags in the docker registry for my project
• If a new tag is discovered, create a new namespace in Kubernetes for it and deploy my project there using the helm chart
• The helm chart should use the corresponding image from the docker registry
• If a new version of the image is pushed, the project instance in the existing namespace should be updated
• If the image tag is deleted in the docker registry, the whole namespace and all of its contents should be deleted from Kubernetes

I am quite new to Flux. While I have some experience with Kubernetes and helm charts, I'm having a hard time figuring out how to implement what is mentioned above.

Is this even possible and if so, how could I achieve this?

[matheuscscp]

Yes, you can do it with Flux Operator's ResourceSet + ResourceSetInputProvider of type OCIArtifactTag (or equivalents for each cloud provider registry).

See this guide for an idea of how ResourceSet works:

https://fluxcd.control-plane.io/operator/resourcesets/github-pull-requests/

Docs here:

• ResourceSet: https://fluxcd.control-plane.io/operator/resourceset/
• ResourceSetInputProvider: https://fluxcd.control-plane.io/operator/resourcesetinputprovider/#type

[plorenz-etes]

Thank you so much, this is the perfect solution!