Building a replacement Rundeck Server

[Roger McCarrick]

Rundeck 4.15 on Red Hat

My Rundeck uses MS SQL 2019 as it's database.

I currently have 2 RD 4.15 community version servers sharing the database.

They also share the logs on a network share.

Users get to Rundeck via a Netscaler and it hits one rundeck front end or the other and they log in with active directory.

So kind of mimicking the commercial version.

Here is what I want to do.

Deploy a new Rundeck server and install Rundeck 5.13, while keeping my 4.15 servers running.

Point it at the same SQL server and logs, and active directory.

So just as I pointed my 2nd 4.15 RD server to the database, and immediately saw all the projects and jobs, I'm hoping the same will be true for the new 5.13 server.

My concern is that 5.13 alters the database in some way that no longer works with 4.15.

This is my roundabout way of upgrading my 4.15.

Also, one reason for this is I want to get off the Red Hat VMs in VMware and deploy Rundeck in a Kubernetes cluster.

So basically my questions is can the 2 versions.
If not .. is there a good guide to upgrade the from 4 to 5?

[rac...@rundeck.com]

Hi Roger,

Deploy a new Rundeck server and install Rundeck 5.13, while keeping my 4.15 servers running.

The problem in that scenario is the database sharing between different versions. That’s not recommended.

The best approach is to backup your rundeck instance and database, upgrade in a non-prod system first (following this and this), and then do it on your main environment

Greetings.

​