# Replace custom node driver

**URL:** <https://forums.suse.com/t/replace-custom-node-driver/19639>\
**Category:** General\
**Created:** [February 26, 2021, 5:17pm UTC](https://forums.suse.com/t/replace-custom-node-driver/19639 "2021-02-26T17:17:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssimeth](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@ssimeth](https://forums.suse.com/u/ssimeth)\
**Post date:** [February 26, 2021, 5:17pm UTC](https://forums.suse.com/t/replace-custom-node-driver/19639/1 "2021-02-26T17:17:51Z")

</div>

I deployed a cluster with a custom node driver and want to update it to the newest version, which provides more features →

[https://github.com/JonasProgrammer/docker-machine-driver-hetzner/releases/download/3.2.0/docker-machine-driver-hetzner\_3.2.0\_linux\_amd64.tar.gz](https://github.com/JonasProgrammer/docker-machine-driver-hetzner/releases/download/3.2.0/docker-machine-driver-hetzner_3.2.0_linux_amd64.tar.gz)

But when I try to deploy a new node with the new driver, it looks like Rancher uses the old driver, which does not provide the new features. So it ended up in an error state:

“Flag provided but not defined: -hetzner-networks; Timeout waiting for ssh key”

Is there a way to tell the cluster to use the new driver?