konveyor / methodology

methodology for modernizing applications to Kubernetes
Apache License 2.0
15 stars 6 forks source link

Methodology questions #6

Open brunoborges opened 1 month ago

brunoborges commented 1 month ago

Hey friends,

First and foremost, the Methodology doc is great, and there is a lot here to unpack. But before I delve into details, I wanted to ask if the methodology is purposely meant to narrow scope towards Kubernetes, or if it was just a matter of initial scope.

The reason I ask is because the way I read the methodology, is that it could well be tailored to other scenarios such as Cloud PaaS adoption (instead of Kubernetes specifically).

When I look at Konveyor, I see a Platform for Migration and Modernization, where tools and methodologies can help teams achieve their goals regardless of the deployment target; in other words, it may or may not be Kubernetes!

Hope this sparks a great discussion!

Bruno

rromannissen commented 1 month ago

Hi Bruno,

You are spot on! First of all, let me tell you that this document is quite outdated at the moment, and we haven't made any progress on it for a while. Almost a couple years ago, Konveyor transitioned from being an umbrella community with multiple projects under it (Tackle, Forklift, Crane and Move2kube among others) to the fully fledged and unified project that it is today. The conductive thread across all these projects was Kubernetes adoption, and in the current project it remains a primary target, but things are open ended for the adoption of cloud native technologies in general.

So going back to the methodology itself, yes, I think it's not restricted to k8s for the most part (although there are some specific things related to it), and it could be applied to multiple scenarios. Originally this was thought as a way to somehow open source the migration and modernization methodology we had used at Red Hat Consulting for years, to use it as a starting point for a discussion with other vendors, GSIs and practitioners to come up with something that could be universally used in these scenarios with the support of the Konveyor tooling.

I would be glad to get back to the drawing board and refine (or redefine!) this with your help, and maybe incorporate some of the approaches and techniques your field practitioners use to tackle large migration and modernization engagements.