kube-jenkins-imager | functional implementation of the automated image building | Continuous Deployment library

I'm trying to get Selenium Grid and Jenkins working together in GKE.

I found the Selenium plugin (https://plugins.jenkins.io/selenium) for Jenkins, but I'm not sure it can be used to get what I want.

I stood Jenkins up by following the steps here: https://github.com/GoogleCloudPlatform/kube-jenkins-imager ( I changed the image for the jenkins node to use Jenkins 2.86 )

This creates an instance of Jenkins running in kubernetes that spawns slaves into the cluster as needed.

But I don't believe that this is compatible with the Selenium plug-in. What's the best way to take what I have and get it working with this instance of Jenkins?

I was also able to get an instance of Selenium up and going in the same cluster using this: https://gist.github.com/elsonrodriguez/261e746cf369a60a5e2d ( I dropped the version 2.x from the instances to pull in the latest containers. )

I had to bump the k8s nodes up to n1-standard-2 (2 vCPUs, 7.5 G Memory ) to get those containers to run.

For this proof of concept, the SE nodes don't need to be ephemeral. But I'm unsure what kind of permanent node container image I can deploy in k8s that would have the necessary SE drivers.

On the other hand, maybe it would be easier to just use the stand-alone SE containers that I found. If so, how do I use them with Jenkins2?

Has anyone else gone down this path?

Edit: I'm not interested in third-party selenium services at this time.