July 2022 Summaries

The upcoming V3 release aims to incorporate all features from V2 by September, including infrastructure logs, environment variables, and deployment rules, to improve debugging, transparency, and cloud cost optimization. Infrastructure logs will enhance visibility and automatically display error information, while a new approach to environment variables merges them with secrets for easier management. Deployment rules, already present in V2, allow for efficient resource management and can significantly reduce cloud costs by up to 60% by optimizing resource usage when applications are inactive. These features aim to streamline operations, allowing developers to focus on more critical tasks, and the transition to V3 is supported by feedback from Alpha testers who help identify bugs and improve functionality. The V3 features will be accessible from specific tabs within the console, promising users an enhanced experience with simplified navigation and management tools.

A preview environment allows developers to test code changes in isolation before merging them into the master branch, offering a temporary and feature-specific testing space that mimics production or staging environments. This setup facilitates efficient testing and collaboration among developers, QA engineers, and product managers by providing a unique URL for each feature branch, thus enabling live testing without affecting other features. The benefits of preview environments include increased ownership and autonomy for cross-functional teams, shorter feedback cycles, faster delivery of product updates, improved review processes, enhanced product quality, and reduced costs due to their ephemeral nature. Despite the advantages, setting up and maintaining these environments can be complex and resource-intensive for DevOps teams. Tools like Qovery aim to simplify this process by integrating preview environments with platforms like AWS, making it easier for DevOps teams to manage these environments while still reaping their numerous benefits.

Maintaining multiple development environments, including production, staging, user acceptance testing (UAT), development, and preview environments, is crucial for enhancing team productivity, ensuring zero downtime, improving security, and facilitating rapid product releases. Each environment serves a specific purpose, with the production environment being the live server for customer interactions and the development environment catering to initial code deployment and testing by developers. Staging acts as a bridge for testing before production, while UAT allows for customer testing to ensure product viability. Preview environments, also known as ephemeral environments, offer flexibility by automatically creating isolated environments for pull request verification, thereby shortening release cycles and reducing costs. These structured environments improve the quality of software and customer satisfaction by allowing iterative testing and feedback, ultimately helping businesses achieve their goals more efficiently.

Qovery offers a fast and versatile solution for deploying applications on AWS, allowing users to set up an Elastic Kubernetes Service (EKS) with necessary components like VPCs and ACLs in just 30 minutes. It provides multiple interfaces, including a web console, CLI, API, and Terraform, with a focus on open-source and extensibility. Users retain control over their Kubernetes clusters while benefiting from automated updates and infrastructure maintenance managed by Qovery. The platform supports cloning environments with a single click, facilitating testing and development without impacting production. Qovery's open-source commitment is evident in its community-driven projects and tools, such as the Qovery Engine and Replibyte. Trusted by numerous companies, the platform integrates seamlessly with existing CI, WAF, and GIT systems, enhancing Kubernetes' capabilities without altering its core functionality.

The guide outlines three practical tips for optimizing application management and cost-efficiency using Qovery. It begins with a method for filtering logs by pod name to streamline log analysis and reduce time consumption. It then highlights cost optimization strategies by employing Deployment Rules to deactivate development environments outside working hours, potentially cutting cloud expenses by up to 60%. Lastly, it describes how to utilize clickable commit messages during rollbacks, allowing users to quickly access specific commits in their git repository. These tips aim to improve user experience and operational efficiency, inviting further community engagement for additional insights.

Qovery has introduced its Console V3 in Alpha testing, highlighting improvements in developer experience and transparency compared to V2, with a demo available for detailed insights. The company has shifted from AWS EKS to a cost-effective AWS EC2 option for hosting applications, particularly suitable for development and hobby projects, despite potential outages due to single Availability Zone reliance. Slack integration now allows for automatic team notifications based on app changes, and Terraform integration enhancements include VPC peering and API token usage. A new API feature, advanced settings, allows for customization of application parameters and deployment delay settings to better manage long boot times. Additionally, Qovery has made several updates, such as a new pricing slider, preview environment URLs, log filtering by pod name, and GitHub permission handling, with ongoing developments tracked in their Changelog.

Qovery has announced official support for Karpenter in all Managed AWS EKS clusters, highlighting its potential as a cost-effective alternative to the Cluster Autoscaler. While the Cluster Autoscaler adjusts Kubernetes cluster sizes based on resource availability and underutilization, Karpenter, launched by AWS, optimizes pod placement and reduces billing costs by automatically provisioning the necessary compute resources for Kubernetes clusters. Although both solutions have their merits, Karpenter is particularly advantageous for significant workloads, whereas the Cluster Autoscaler is more stable and widely used for production environments. Qovery considers Karpenter suitable for pre-production, staging, or testing phases, with the hope that other cloud providers will adopt it as a new standard in the future.

Heroku has long been favored by startups for its simplicity and ease of use, enabling quick application deployment without the need for extensive server management. However, as startups grow, they often encounter challenges with Heroku's limited flexibility, high costs, and scalability issues, prompting consideration of alternatives like AWS. Despite these downsides, many startups continue using Heroku due to its strong developer experience and the ability to swiftly deliver customer value without deeply investing in DevOps resources. The main reasons for migrating away from Heroku include its lack of control, rising expenses as businesses scale, limited scalability and resource options, and frequent outages, such as the notable incident on June 10, 2025. When choosing a new platform, startups prioritize security, developer experience, and support, among other factors, as they seek a more flexible and cost-effective solution that can sustain their growth.

V3 represents a major product evolution over the past year, offering significant enhancements such as an improved developer experience, sleek new logs, and an open-source repository. Benjamin, a software engineer at Qovery, provides a comprehensive overview of these updates, highlighting the key features and improvements in the new version. Additionally, a demo video is available to showcase the capabilities and innovations introduced with V3.

Qovery is transitioning from using AWS EKS, which incurs a monthly cost of $220, to a more cost-effective solution utilizing AWS EC2, priced at $20 per month, for deploying applications. This change involves using an AWS EC2 instance instead of an AWS EKS Kubernetes cluster, making it suitable for hobby projects and testing environments. The primary distinction between AWS EC2 and AWS EKS is the number of Availability Zones (AZ), with potential outages in EC2 being acceptable for development and hobby projects. Qovery provides a straightforward setup process for users to create a cluster, select AWS, and choose EC2, catering to those looking for a budget-friendly solution for non-production applications.