k3d config options about ctlptl HOT 5 CLOSED

aw thanks ❤️

Would a k3d configuration just include the flags here?
https://k3d.io/v5.2.0/usage/commands/k3d_cluster_create/
or alternatively, we could add a CreateFlags array like we did for minikube (https://pkg.go.dev/github.com/tilt-dev/[email protected]/pkg/api#MinikubeCluster)

is this mainly to add volumes, or are there other flags that are important?

from ctlptl.

@nicks thanks for the response.

I hadn't thought through implementation much, tbh, but the specific use case that made me request this was adding port forwards.

from ctlptl.

ooh that's good to know. are you using the portforwards to test an ingress? i've been thinking about better "standard" setups for dev clusters with ingresses.

from ctlptl.

I'm using Tilt to hack on several different projects, but most of these projects have dependencies I'm not actively hacking on and don't care to build/deploy from source since helm charts are readily available. So I'll have a make target like dev-cluster-up that uses ctlptl to launch the cluster and then immediately installs those prereqs. In many of those cases, it's also useful for me to also be able to connect directly to those dependencies from the physical host.

Right now I can do all of this with ctlptl + kind, but k3d comes up a bit faster, so I'd be entertaining the switch if this worked.

from ctlptl.

@nicks I'd love to be able to disable traefik. It could be the default for ctlptl if you're looking to "standardize".

apiVersion: k3d.io/v1alpha4
kind: Simple
options:
  k3s:
    extraArgs:
      - arg: --disable=traefik
        nodeFilters:
          - server:*

from ctlptl.