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
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
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 focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)