Updating k3d proxy ports on a running cluster

[NesManrique]

I have a running cluster setup with a config file (see below) and among other things installing the nginx ingress controller.

Let's say later, after the cluster is created, I want to add another port (e.g 9906:9906) so it is also forwarded by the k3d-proxy container.

Can I do that somehow without destroying and creating the cluster from scratch?

I've search everywhere in the docs and the internetz with no avail.

apiVersion: k3d.io/v1alpha2
kind: Simple
name: dev-cluster
servers: 1
agents: 0
ports:
  - port: 8080:80
    nodeFilters:
      - loadbalancer
  - port: 8443:443
    nodeFilters:
      - loadbalancer
volumes:
  - volume: "<HOME>/k3d/helm:/var/lib/rancher/k3s/server/manifests/my-manifests"
    nodeFilters:
      - all
options:
  k3d:
    wait: true
    timeout: "300s"
  k3s:
    extraServerArgs:
      - --no-deploy=traefik

[iwilltry42]

Hey @NesManrique, thanks for starting this discussion. 👍
Currently this is not possible.
But I have the feature implemented in the main-v5 branch and it will land in the v5.0.0 release soon-ish.
The proxy container has no state to persist, so you could do it yourself with docker commands if necessary (or build the branch yourself)🤔

[NesManrique]

Good to know.

Thank you for the quick reply!