Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet Migration
-
Subject: ProGet 25 Migration, Database, and High Availability Questions
Hello,
We are currently running ProGet 24.x on Azure Kubernetes Service (AKS).
We are planning to upgrade to ProGet 25.x, as we understand that Microsoft SQL Server support will be not supported by the end of the year.
We therefore have a few questions regarding this migration:-
Database migration:
Do we need to migrate to the internal PostgreSQL database when upgrading to ProGet 25, or are other database options supported? -
High Availability:
How is High Availability implemented in ProGet 25?
Are there specific architecture recommendations for Kubernetes-based deployments or Windows? -
Platform support
Has this High Availability setup been fully tested on Linux pods, or is it currently supported only on Windows-based deployments? -
Performance and load
Our current workload ranges from 500 to 7,000 requests per minute.
Can ProGet 25 handle this level of traffic reliably, and are there any recommended sizing or scaling guidelines?
Thank you in advance for your guidance.
-
-
Just to clarify the support:
We are planning to upgrade to ProGet 25.x, as we understand that Microsoft SQL Server support will be not supported by the end of the year.
We are currently planning to discontinue SQL Server support in ProGet 2027. It will continue to work in ProGet 2025 and ProGet 2026 regardless of when you use the software.
To answer your questions...
- You can continue using SQL Server in ProGet 2025
- Please see Configuring High Availability & Load Balancing, which details the implementation
- ProGet for Linux is supported in a Docker environment; many users will deploy using Kubernetes, but we do not provide charts or templates... only a Docker Installation Guide that you will need to "translate" into pods, etc
- ProGet can handle that traffic, though a lot of factors will determine how much server resources are required; I would start with a two-node cluster and evaluate/consider adding more if needed
Thanks,
Alana
-
Hello,
Thank you for all those information.
I setup the Proget25 into an UAT instance and my question is now more related to the Licence.
Can I use my current Production licence on both environment Prod and UAT or I have to get a new one. Limited perhaps
-
ProGet is licensed per instance (i.e. installation), you will need a separate license if you wish to maintain a production and non-production instances of ProGet. See the official Licenses for Non-production / Testing Environments for more details.
For things like a one-off, cloud-migration, using a Trial license (which you can get from My.Inedo.com) is fine.
Thanks,
Alana
