Manually Trigger Preview Environments with Create On Demand Feature
Preview Environments Redefined
Our Preview Environment feature has always provided an invaluable tool for developers. It allows teams to seamlessly create a replica of their production environment, an invaluable tool for testing, debugging, and validating new features before they reach your users. But as we worked, listened, and learned from your experiences, we realized there was room for even more enhancement.
Today, we are delighted to introduce an update that refines the whole process of using preview environments, making it more flexible and tailored to your specific needs. Our new functionality lets you spawn a preview environment on demand, right from your Pull Request/Merge Request, giving you more control than ever before.
The Power of Choice
Previously, a preview environment was created for every pull request, a process that was straightforward but could sometimes lead to unnecessary previews, such as when you simply updated a README file. But with our new update, we've introduced a significant change - choice.
You now have the option to decide whether a preview environment should be triggered manually or automatically for every PR. This not only gives you greater control over your workflow but also helps to avoid unnecessary usage and streamline your processes.
Introducing: "Create on Demand"
Our update introduces a new flag within the preview environment settings: "Create on Demand." When the Preview Environment feature and this flag are activated, the preview environment won't be created automatically.
Instead, the process is as follows:
- A message is dropped on your PR asking if you want to create a preview environment. You'll also get a list of environments where the Preview Environment feature is active (if you have multiple environments), along with the command to add as a PR comment to trigger the preview.
- You will have to add the command in a comment to trigger the preview.
- The preview creation is triggered, and your preview environment is deployed.
We know you use different Git providers, and we've got your back! We've jazzed up the flow to make it more playful and all about you, ensuring our cool new feature fits like a glove wherever you're using it.
Watch the quick demo of this fantastic new feature below.
Changing the Game in Software Development
Our latest feature update is more than just a cool new tool. It's a paradigm shift that puts the power back into the hands of developers, giving you the flexibility and autonomy you need to optimize your workflow and maximize efficiency.
So get ready to experience a whole new level of convenience and control in your software development process. We're excited to see how you'll leverage this feature to streamline your workflow, reduce unnecessary usage, and ultimately, create better software, faster.
We're looking forward to your feedback on this exciting new feature! Happy coding!
.svg)
.svg)
.svg)
Suggested articles
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes is an open-source container orchestration engine. At enterprise scale, it abstracts infrastructure to automate deployment, scaling, and networking. However, managing hundreds of clusters introduces severe Day-2 operational toil, requiring agentic control planes to enforce global governance, security policies, and cost optimizations across multi-cloud fleets.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
.webp)