webdrivermanager VS jkube

Haven't used webdriver in a while, look at playwright as an alternative. But you should use web drive manager https://github.com/bonigarcia/webdrivermanager

On lines 5 to 9, there’s the implementation of the createDriver() method creating a local browser instance using the WebDriverManager library. Note that the new browser instance is using the getOptions() and I will explain it in a minute.

https://github.com/bonigarcia/webdrivermanager you might check this guy out too. It handles web driver management.

You can use WebDriverManager (https://github.com/bonigarcia/webdrivermanager/) to handle the download and set up of the chrome driver if you are using java.

This (https://github.com/bonigarcia/webdrivermanager) is an open-source Java library that carries out the management (i.e., download, setup, and maintenance) of the drivers required by Selenium WebDriver (e.g., chromedriver, geckodriver, msedgedriver, etc.) in a fully automated manner.

This version of ChromeDriver has not been tested with Chrome version 91. I think your chrome version is no the same as a web driver use this https://github.com/bonigarcia/webdrivermanager

I've experimented with jkube, and had pretty decent experiences with it. But it is very much it's own thing, and is kind of a very Maven-oriented workflow that replaces things like, well, Helm. (Which, IMO, isn't a bad thing. Helm is still wonky in many ways.) I bring helm up, because the place where I was experimenting with this went full steam on helm templating in a way that was wildly stupid. There was this bizarre approach of using helm calling terraform instead of using the kubernetes terraform operator (don't get me started). jKube didn't work that well with that, but only because of the utter stupidity.

Eclipse JKube GitHub