Kestra

A new job is on the market: Frontier Engineer. What is it? Someone who decides which process steps an AI agent can own, which must stay deterministic, who approves in between, and what happens when the agent gets it wrong. → Split each process into agentic vs fixed steps → What the agent returns, who approves, what the fallback is → Give agents the right tools and access → Make every agent run observable → Put it all under change control That's what a workflow orchestrator has done for years. Learn more: https://lnkd.in/eTKqS8EX

Kestra Academy is open. 🎉 Kestra now has a place to learn it and a certification to show you did. Four courses, built by the team that builds the product: 🧱 Kestra Fundamentals. The building blocks of a workflow, the syntax, and how the engine runs it. 🏗️ Infrastructure Automation. Servers, clouds, and day-two operations, orchestrated from one place. 🤖 AI Workflows. Agents, models, and MCP tools inside the same flows as everything else. 📊 Data Pipelines. Move, transform, and monitor data end to end. Each course ends with its own certification. Pass it and become Kestra Certified, with a credential you can add to your LinkedIn profile. Start with Fundamentals, then pick the track that matches your work. 👉 https://academy.kestra.io/

Benjamin Squire hosted DevRel's first Virtual User Group for Graph Analytics, and we were honoured to have our first community speaker talk about building a data pipeline with dbt Labs and orchestration tool Kestra Want to catch up and learn about 5 algorithms, get some top tips from Ben and Holly and learn about identity resolution for marketing? Then you can watch it back here https://lnkd.in/ezxbv9kV We'll be hosting another event so stay tuned. You can install our app, which comes with a 30-day trial https://lnkd.in/ekRnPvGr Alexander Erdl Kapil Hetamsaria Anurag Tandon Kat Eeds Keaton Crowe Ricardo Garita

Hacktoberfest is a week away. Can we please not snipe each other's issues this year? It happened to me again today. I found a "good first issue," commented "Can I take this?", and started digging into the codebase. Thirty minutes later, someone who never said a word on the thread linked a PR that closes it. No comment. No "hey, are you working on this?" Just a drive-by PR. And October hasn't even started yet. Every year, Hacktoberfest brings a flood of new contributors, and that's a great thing. But it also brings a flood of PR-count chasing: people racing to grab every good first issue they can find, ignoring the thread, ignoring whoever asked first, and burying maintainers in duplicate PRs. This isn't how open source is supposed to work. Open source runs on trust and communication, not speed. If you're joining Hacktoberfest this year (or any time), here's the protocol most healthy projects expect: 1. Read CONTRIBUTING.md first.CONTRIBUTING.md first. Many projects require you to be assigned before you open a PR. 2. Comment on the issue before you start working. Let people know you're on it. 3. Check the thread. If someone already asked to take it, respect that. Ask if they're still working on it, or pick another issue. 4. Wait for a maintainer to assign you if that's how the project works. 5. If an issue looks abandoned, ask politely: "Are you still working on this? Mind if I take it?" Give them a reasonable window before jumping in. 6. Don't farm good first issue labels. If you're experienced, leave them for people making their first contribution. 7. Quality over count. One thoughtful PR is worth more than five rushed ones. Maintainers remember the difference. To maintainers heading into Hacktoberfest: please consider assigning issues when someone asks, or adding a clear "claim before you code" rule. October gets chaotic, and a little structure saves everyone wasted effort and bad blood. Sniping a PR might get you a merge and a checkmark on your progress. But it costs the community something much bigger: the newcomer who quietly decides open source isn't for them. This Hacktoberfest, be the contributor people want to work with. 🤝 #Hacktoberfest #OpenSource #GitHub #DeveloperCommunity #OSS

A couple of weeks ago, we released Kestra 2.0, a huge milestone for the team after months of hard work! Around the same time, my personal OSS project Jikkou hit 300 stars ⭐ on GitHub. Sure, it’s not the latest viral AI tool 😅, but I’m really happy to see the project growing over the years. Seeing both happen at once felt like a good excuse to write down how they fit together. I just published a new blog post on building a fully automated, human-in-the-loop provisioning service for #ApacheKafka using Kestra and Jikkou. #OpenSource #AivenFreeTier #Automation #Orchestration #Kestra

Dear DevOps Engineers, Never let AI take control of infrastructure. Imagine a developer tells an AI agent: “Create a production environment for my new service.” The agent can understand the request, decide what infrastructure is needed, and even generate the Terraform code. But should it directly run terraform apply? Probably NOT. Production infrastructure isn't just about generating code. You need to: → Plan & validate the Terraform → Check policies & permissions → Get approvals for sensitive changes → Apply & verify the changes → Handle failures & audit the execution The problem is that if AI generates and executes the code, who will orchestrate all that is needed to safely run it in production? That’s where platforms like Kestra can help. With Kestra 2.0, DevOps Engineers can define the workflows that AI agents are allowed to use and expose those workflows as MCP tools. The agent can then discover these tools and invoke the right workflow, while Kestra handles the actual execution and governance. Instead of giving the agent direct access to Terraform, cloud APIs and production credentials, expose a governed capability like ->  “provision_production_environment” The Kestra workflow can then handle the execution: Plan → Policy Check → Approval → Apply → Validation → Audit And this brings four things critical for production: Predictability. Correctness. Governance. Observability. In a nutshell, AI decides what. Orchestration controls how. This is the future of infrastructure management using AI + DevOps. Thanks to Kestra for addressing this and also collaborating on this post. Kestra 2.0 is open source and FREE to get started. https://fandf.co/4r7kRT7 Kestra Github repo:  https://fandf.co/4iLYNeX This is a very useful AI + DevOps implementation. If you want a full implementation on YouTube, just comment “Kestra” and I will do it.

For those of you who want some coding experience: Kestra's Hacktoberfest runs from October 1 through October 31, and it's a great chance to develop your reputation as an open-source contributor. You can participate in a couple of ways: 1. Fix an issue in Kestra's core or plugin repositories. 2. Build a reusable Kestra workflow in YAML and submit it to the kestra-io/blueprints repository. You will find ~200 issues labeled "good-first-issue." Pick one, write the code to close it, and submit a PR with before-and-after screenshots that show the change. If you build a workflow, your submission must include at least 3 runnable tasks, 1 flow task, 1 trigger, and at least 1 non-core plugin. They should all work together in a flow other people can reuse. You know you made it when the Kestra maintainers accept and merge your PR. There are prizes, by the way: • First place → MacBook Neo • Second place → Apple iPad • Third place → Apple gift card To learn more, check out the official landing page: https://fandf.co/4hvutE5 To participate, make sure to register using the form below: https://fandf.co/4xuHYIM When you fill out the form, select my name under "Referred by." Thanks to the Kestra team for partnering with me on this post.

This Hacktoberfest, you can fix a real open-source issue or build something other developers will actually use. And win a prize for doing so. I’m excited to be part of the Kestra Hacktoberfest Hackathon this year. There are two tracks you can enter. Track 1: Fix something real in the codebase. Kestra has identified and scoped a number of issues across its core and plugin repositories. They’re tagged good-first-issue, so you can find one that interests you. Once you find one, comment on it to let others know you’re working on it for Hacktoberfest, and start contributing. Track 2: Build a flow other people will reuse. Create a blueprint, a ready-to-use flow template that someone else can pick up and run. The best place to start is with something you’d find useful yourself - scratch your own itch! If you need inspiration, browse Kestra’s existing blueprints or check out the Code Review Agent from Coding Challenges: https://lnkd.in/e4K5U-UY There are prizes for each track: 🥇 1st place: 13” MacBook Neo 🥈 2nd place: Apple iPad 🥉 3rd place: $150 Amazon gift card Submissions close on 31 October and the winners will be announced in November. You can find all the details and register to take part here: https://fandf.co/4rHeVAR We’re also kicking things off with a launch livestream at the start of October - more details to follow. If you’re thinking about taking part, go register now. If you have any questions, please ask in the comments.