@Marvin If I'm using a k8s worker, how can I add the logic that for each pod spawned it has to add a nodeport?

It seems there wasn't much detail specifically about adding NodePort to pods in the found documentation. However, we can derive from general Kubernetes practices. To add a NodePort to the pods spawned by a Prefect Kubernetes worker, you'll need to customize the Kubernetes job template used by Prefect. Here’s a high-level overview: 1. Define a Service: Create a Kubernetes Service with type

NodePort

to expose your pods. 2. Customize the Job Template: Use a custom Kubernetes build script to incorporate the service into the Prefect flow. Here’s a simple example of how you might define a Service in a Kubernetes manifest:

yaml
apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: NodePort
  selector:
    app: my-app
  ports:
    - protocol: TCP
      port: 80
      targetPort: 9376
      nodePort: 30007

Include this service manifest in your deployment along with your Prefect Kubernetes worker setup. For the job template, you might customize it as follows:

yaml
apiVersion: batch/v1
kind: Job
metadata:
  name: my-prefect-job
spec:
  template:
    spec:
      containers:
      - name: prefect-job
        image: your-prefect-image
        env:
          - name: PREFECT_API_URL
            value: YOUR_PREFECT_API_URL
          - name: PREFECT_API_KEY
            value: YOUR_API_KEY
      restartPolicy: Never

For specific implementation details, you should refer to: - Prefect Kubernetes Deployment Guide This should serve as a starting point for configuring your Kubernetes worker to include NodePort. If you encounter specific issues, Prefect's GitHub repository or community forums might have more tailored advice.