Unknown executor name: k8s

[gwright99]

Summary of Issue

Configured Launchpad pipeline launched from tw fails with error ERROR ~ Unknown executor name: k8s. Same pipeline works fine when launched via Seqera Platform UI.

Scenario Reproduction

Seqera assets:

• Seqera Platform Enterprise 24.2.5_9f5ee41
• Nextflow 25.04.6
• TW 0.15.0 c420fcf (jar-type)

CE infrastructure:

• EKS K8s (PVC-type)
• Custom nf-launcher (651706780852.dkr.ecr.us-east-1.amazonaws.com/nf-launcher/unprivileged:v4)
  • Derived from public.cr.seqera.io/platform/nf-launcher:j21-25.04.6

Pipeline:

• hello
• See screenshot for config
• Seqera resources can see additional setup information here: https://github.com/seqeralabs/cx-field-tools-nf-launcher-nonroot

Commands

tw -v launch -w <WS_ID> hello_noplugin --launch-container=651706780852.dkr.ecr.us-east-1.amazonaws.com/nf-launcher/unprivileged:v4

Expectation

Given that tw-launched pipeline is targeting a K8s CE, Seqera Platform should automatically add the necessary K8s plugin.

plugins {
  id 'nf-k8s'
}

Actuality

Automatic addition is done for pipelines launched directly from Seqera Platform, but not the equivalent pipeline launched from tw. You need to explicitly add the plugins block to the pipeline config to get the tw-launched version to succeed.

Screenshots

Pipeline config

Error when tw-launched instance doesnt have plugins explicitly defined

Success of same pipeline when invoked directly from Seqera Platform

tw-launched instance working when plugins explicitly defined