![]() Nextflow submits tasks as Pods by default, which is sort of a bad practice. So here we go! New features Submit tasks as Kubernetes Jobs In this blog post, I’d like to show off all of these improvements in one place. So, I set out to make Nextflow + K8s great! Over the past year, in collaboration with talented members of the Nextflow community, we have added all sorts of enhancements to the K8s executor. While Nextflow’s extensible design makes adding features like new executors relatively easy, support for Kubernetes is still a bit spotty. You see, Nextflow was originally built for HPC, while Kubernetes and cloud batch executors were added later. The guide has helped many people, but for me it provided a map for how to improve K8s support in Nextflow. One of my first contributions was a “ best practices guide” for running Nextflow on Kubernetes. Which brings me to the topic of this post: Nextflow and Kubernetes. ![]() While I tried to avoid contributing code to Nextflow as a student (I had enough work already), now I get to work on it full-time! I have written Nextlfow pipelines for bioinformatics and machine learning, and I even wrote a pipeline to run other Nextflow pipelines for my dissertation research. I have run Nextflow just about everywhere, from my laptop to my university cluster to the cloud and Kubernetes. I work on a number of things at Seqera, but my primary role is that of a Nextflow core contributor. I joined Seqera in November 2021 after finishing my Ph.D. Hi, my name is Ben, and I’m a software engineer at Seqera Labs.
0 Comments
Leave a Reply. |