Hi @juanpanie
Happy new year to you as well:)
You can, and depending on your traffic and geo distribution, probably SHOULD export your media content onto a remote storage and then serve it from CDN. With Amazon, you can export to an S3 bucket and use CloudFront for serving the content.
Out of the box, Kaltura supports creating remote storage profiles that can export the content using S3, SFTP and FTP [though FTP is not recommended for several reasons]. I never used Azure for that but if it’s capable of using SFTP then it should also work out of the box.
Once that’s done, you also need to create a delivery profile so that the content is served from CDN.
You can configure the remote storage profile so that files exported to the remote storage are then deleted from the local content dir/NFS volume [/opt/kaltura/web/content] but be aware that if you do so, you will not be able to reconvert these source files or perform other operations like trimming and clipping.
Either way, you want to leave a healthy amount of free space on your Kaltura nodes root partition and the /opt/kaltura/web/content partition [which may or may not be the same thing] because the first step will ALWAYS be to upload the files to /opt/kaltura/web/content/uploads, then perform the transcoding operations to create the different flavours and place them under /opt/kaltura/web/content/entry only then can the media files be exported to the remote storage.
Hope that helps clarify things,