Closed hi120ki closed 1 year ago
Hello @hi120ki
I updated the Free5GC container images to v3.2.0. All container images are available on our towards5gs Dockerhub Organization. I've not yet created the v3.2.0 tag for our images but all latest version of Container images have been built from Free5GC v3.2.0. For example, for UDR, the latest version corresponds to Free5GC v3.2.0.
The next step is to update NF configurations in the Helm charts and point to the latest images (for tests) by setting the appVersion
to latest for all Helm charts. I will do it next (I'm currently working on another topic) but if you want to contribute you're welcome I can help you. Once done, I will tag our private Github repository and workflows will tag the Docker images on DockerHub. Then, updating the project to v3.2.1 will be easier (I guess that there was no changes in configuration files).
About publishing Docker images, this is in our plans but we need to check the licenses in my company. I don't think it is feasible before September. The idea is to make all Dockerfiles in a dedicated folder within our project.
Bests Raouf
Thank you for updating image.
I'm creating an environment for testing, and I faced an issue #49 .
Could you give me some comments? Thank you.
Hi, a PR is created. Could you review especially about the UPF config?
Thank you.
Since the PR is already validated, I will close this issue. Many thanks for your contribution.
Hi, thank you for the maintenance of this project. This project is so helpful for me.
About a month ago, free5gc released v3.2.0(today's latest release is v3.2.1) that includes the migration of upf implementation from Clang to Golang. I'd like to test how UPF that is created by Golang works in Kubernetes, but towards5gs-helm project supports v3.1.1.
Could you consider updating free5gc images?