daemonless mode in kubernetes?

[dev-samples]

From jenkins running in kubernetes I currently build and push an image with:

  stage('buildx create') {   
    sh """
      docker buildx create \
      --use \
      --name k8s node-amd64 \
      --driver kubernetes \
      --driver-opt image=moby/buildkit:master
    """ 
  }    

  stage('buildx build and push') {   
    sh """
      docker buildx build .  \
      --push \
      -t internal.reg/myimage
    """
  }

But after the build completes the buildkitd pod is still running (created by docker buildx build).

Is it possible to specify to buildx that it should build using buildkit daemonless:
https://github.com/moby/buildkit#daemonless

I can of course manually remove it with:

  stage('buildx remove builder') {
    sh """
      docker buildx stop
      docker buildx rm --force
    """
  }    

but since that functionality already seems to be available in buildkit (buildctl-daemonless.sh) might be there is an option to specify that to buildx?

[rwilson-release]

The buildx Kubernetes driver uses a Kubernetes Deployment which is a long-lived way of controlling running pod states. daemonless refers to the docker container running the buildkitd process in the background (which would exit when you are finished). The confusion is that Kubernetes pods that are part of a deployment are long-lived containers that process build jobs for you.

In my search, many people like myself are trying to improve on the Deployment model to use a Kubernetes Job model instead.