Do, still, I need to run the Flywydb image as Kubernetes Job to run database migrations from Springboot deployed in Kubernetes (EKS & Openshift)?
I see some references of Flyway being configured that way. However, in case of Springboot, Flyway migrations are run as part of start cycle.
Am I missing something?
You have multiple options: You can either use flyway as part of your application or you can use a separate container, for example as an initContainer in Kubernetes. If you feel more comfortable with having flyway as part of your application and run in similarly to your local development environment, just go ahead.