Restart a Service, Force Run for Lifecycle Jobs and Cronjobs...
Hi there 👋🏻 fellow Changelog readers; we are excited to introduce our latest update, packed with new and improved features to boost your experience! You can now restart a service, force-run jobs, and customize your own subdomain. Plus, with the addition of extra advanced settings, you'll have even more control and power at your fingertips. Empower yourself and unleash the full potential of our platform. Let's keep pushing the boundaries together!
The Restart Service feature allows you to restart your service pods without having to deploy a change to make this happen. This feature is only available when the deployment status is Deployment OK and for individual services. To learn more about it, please refer to our Restart Service documentation.
You can now force the execution of a job at any time by selecting the desired event to trigger for a lifecycle job and Cronjobs. For more information on this feature, please see our Force Run for Jobs documentation or Force Run for Cronjobs documentation.
A new URL has been added for each preview environment, with the format: prId-srvName-envSourceName.cluster_domain. In addition, you can define custom subdomains within the domain section, such as [my-cool-subdomain.cluster_subdomain](<http://my-cool-subdomain.zc531a994.rustrocks.cloud>) . To learn more about it, check out the documentation.
We are pleased to announce the addition of Cluster Advanced Settings! Not yet available on the interface, to further fine-tune your Qovery infrastructure, you can set advanced settings through the Qovery API endpoint.
While you can find every Cluster Advanced Settings in the documentation, here is a sneak peek of what you will be able to find there:
- The cloud watch retention setting can now be found in the advanced settings section. For instructions on how to use it, please refer to our documentation.
The Nginx advanced settings now include the options for
- denylist: restrict IPs accessing your applications
- basic authentication: so you can now add basic authentication natively into your apps
As shared in our roadmap, we have been preparing all the necessary updates to migrate your cluster to the 1.23 version. Last week was the first step of this process, and 1.23 is now the default version for any new cluster. To know everything about this upgrade, check out this page on the Forum, where we will keep you updated and where you can ask any questions you might have about it.
Initially, Qovery included support for multiple cloud providers, including DigitalOcean, due to its affordable pricing for small businesses and projects. However, after a few years, we saw that DigitalOcean fell below our expectations for delivering high-quality production experiences for our users. As a result, we have decided to discontinue support for DigitalOcean until significant improvements are made to their cloud offering. Our users rely on Qovery for transparency, and it is this commitment to honesty that led us to the decision to no longer offer support for DigitalOcean. Here is an article about it if you want to know more.
We would like to inform you that the /restart endpoint has been migrated to /redeploy so you should now use /redeploy instead.
- [V3] Cluster page header and settings have been delivered (only general and danger zone)
- [V3] URL format has been updated everywhere (pointing all to new.console.qovery.com)
- [V3] "update services version" feature has been delivered (the old "update all")