The 4 Most Exciting Features Coming For January 2023
Cron Job
Just in case you don't know what a Cron Job is - it is a task to be executed sometime in the future. This is typically used to schedule a job that is executed periodically – for example, to send a report every morning. We expect to release the first version of our Cron Job for December and in GA for January 2023. As for the applications, you can create a Cron Job from a Dockerfile coming from your git repository OR a container image from a Container Registry.
Check out this video from Alessandro (Lead PM @ Qovery) explaining Cron Jobs (and Lifecycle Jobs)
Lifecycle Job
The Lifecycle Job is a task that can be triggered on a specific Environment Event. Here are some concrete examples of where Lifecycle Job is useful:
- Seeding your database when your environment is created.
- Spinning up a MongoDB Atlas instance via Terraform when your Environment is created and cleaning it when it is deleted.
- Spinning up serverless functions on the cloud provider of your choice when your Environment is created and cleaning them when your Environment is deleted.
- In a more general way, you can provide any external resources (not managed by Qovery) with Lifecycle Jobs. Do you need to spin up and clean AWS SQS, SNS, SES, GCP Big Query, and Serverless functions?... Qovery Lifecycle Job got you covered.
Deploy Your Terraform Modules
This is the feature I am personally waiting for the most - Being able to deploy Terraform Modules right from Qovery. Terraform is the most used Infrastructure as a Code tool. We want to ensure that DevOps engineering teams adopting Qovery can re-use all the work they have already done to deploy On-demand and Ephemeral Environments.
Additionally, Qovery will provide a built-in state backend. So, no need to worry about where to store your state file. What about cost control and drift management? We are thinking about everything, and I can't wait to show you what we are preparing here 🔥.
Faster Deployments
Are you annoyed to wait 10 minutes to see all your services deployed? I feel you. That's why our Qovery Engine will support parallel deployment. Your deployment time will be drastically reduced since Qovery can build and deploy your applications in parallel.
What else?
The 4 features above are the biggest ones that we are working on. But we also consider delivering improvements and features like Audit Log and SAML and starting to support GCP as soon as possible. Don't forget to vote for the features you expect to see in Qovery. We prioritize based on your votes and feedback.
.svg)
.svg)
.svg)
Suggested articles
Because various organizations need cloud application and service management that offers different levels of simplicity, cost-effectiveness, or feature sets than OpenShift, this article will review its top alternatives to help readers make an informed decision aligned with their specific infrastructure needs.
Running GPU workloads on EKS has never been easy, until now. With Qovery’s latest update, you can enable GPU nodes, configure GPU access, and optimize costs automatically, all without writing a single line of YAML or touching Helm charts. Qovery now handles everything behind the scenes so you can focus entirely on your applications.
Master Kubernetes deployment strategies: Rolling Update, Recreate, Blue/Green, and Canary. Learn the pros, cons, and use cases to choose the right strategy based on your uptime, risk tolerance, and resources. Simplify complex rollouts with automation.
Confused about which AWS container service to use? This comprehensive guide compares the trade-offs between simplicity, control, and complexity for ECS, EKS, and Elastic Beanstalk to help you choose the right platform for your application.
Planning your ECS to EKS migration? Learn the strategic business case (portability, ecosystem access), navigate the step-by-step roadmap, and avoid common pitfalls (networking, resource allocation). Discover how Qovery automates EKS complexity for a seamless transition.
Is Fargate too simple or Kubernetes too complex for your scale-up? Compare AWS Fargate vs. EKS on cost, control, and complexity. Then, see how Qovery automates Kubernetes, giving you its power without the operational headache or steep learning curve.
Dive into the ultimate FluxCD vs. ArgoCD debate! Learn the differences between these top GitOps tools (CLI vs. UI, toolkit vs. platform) and discover a third path: Qovery, the DevOps automation platform that abstracts away Kubernetes complexity, handles infrastructure, and lets you ship code faster.
Qovery unveils its new brand identity, reinforcing its mission to make DevOps simple, intuitive, and powerful. Discover how our DevOps automation platform simplifies infrastructure, scaling, security, and innovation across the full DevOps lifecycle.
.webp)