- Konveyor is a CNCF project focused on accelerating application modernization to cloud native technologies in a safe and predictable manner at scale
- Related documents for more background on Konveyor:
- Konveyor Project Charter
- Vision for Konveyor's Unified Experience
- Konveyor Application Modernization and Migration Guide
- Where to file new RFEs? -> https://github.com/konveyor/enhancements/issues/new
- Read our enhancements to learn more about design choices and how features are being implemented
- Related documents for more background on Konveyor:
-
Theme: Establish Steps 1->3 of Unified Experience: 'Surface Information -> Make Decisions -> Plan Work'
-
Multi-language analysis support
- A new analysis engine, analyzer-lsp, is being developed to leverage the Language Server Protocol to make additional languages easier to integrate.
- Intent is to replace Windup for Java source code analysis with analyzer-lsp
- Add ability for Golang source code analysis via analyzer-lsp
-
Allow dynamic reporting of analysis data and aggregation across the application portfolio (enhancement: Dynamic reports enhancement)
- Establish ability for machine readable output from analyzer-lsp to aid the Hub to aggregate analysis information across the application portfolio (enhancement: Analyzers Report Format
-
New Assessment module to allow greater customization of questionnaires and usage (enhancement: New assessment module enhancement)
- Introduction of 'Archetypes'
- Intent is to replace Pathfinder with this new module to allow more flexibility
-
-
Theme: Project health
- Establish e2e test strategy
- Establish test framework for rulesets
- Continue creating a library of examples-applications
- Establish Migration Experience User Group to facilitate sharing of use-cases and rules throughout community.
-
Theme: Expand multi-language static code analysis capabilities
- Establish C# analysis for dotnet (analyzer-dotnet-provider), emphasis on usecase of .Net Framework -> .Net migrations
- enhancement: dotnet-provider
- Establish C# analysis for dotnet (analyzer-dotnet-provider), emphasis on usecase of .Net Framework -> .Net migrations
-
Theme: Begin to explore improvements to Step 4 of Unified Experience: 'Do Work'
-
Evaluate if we need to orchestrate execution of multiple components in a Pipeline like approach
- Possible exploration of Tekton for improving orchestration of components
-
Generate migration assets to aid a Migrator modernizing an application
- Considering examples such as
- Guide containerization of a traditional application
- Guide containerization of a Wildfly application to leverage application analysis information to recommend Galleon layers to enable in the image
- Generate Kubernetes resource manifests so the application may be deployed
- Generate resources to enable a GitOps workflow such as ArgoCD
- etc.. more to explore
- Considering examples such as
-
-
Theme: Continue on expanding Rulesets
- Considering examples related to:
- .Net Framework -> .Net
- Wildfly
- Tomcat
- Quarkus
- Netflix OSS -> Kubernetes
- Service Mesh adoption
- Serverless
- and other areas identified from the Migration Experience User Group
- Considering examples related to:
-
Theme: Project Health
- Improve Konveyor user documentation and revisit integrating https://konveyor.github.io/ into https://konveyor.io
-
Theme: Expand multi-language capabilities
- Add in capability to analyze Javascript, Typescript, Python, Ruby, Rust, etc
- Continue to extend capabilities in all providers (richer queries, detect more complicated use-cases)
-
Theme: Experience improvements
-
Improve the experience of application import
-
Improve the experience of executing 'AddOns'
-
-
Theme: Continue to explore new use-cases in Konveyor Ecosystem
- Explore solutions to aid in monolith to microservice
- Improve resource generation
- Explore k8s workload introspection to inform possible issues between versions of Kubernetes
- Expand refactoring scenarios, i.e. explore patterns of leveraging knowledge from static code analysis to aid in automated refactoring to address identified issues (i.e. analyzer-lsp report -> openrewrite recipes to 'fix' code)
- Research if/how AI may be applied to modernization (experiments under https://github.com/konveyor-ecosystem/MLAssist)
-
Theme: Integration with other services
See konveyor/operator/releases for a list of all Konveyor releases or in operatorhub here
- 0.1.0: April 2023
- The effort that was Tackle 2.0 is expanded to become the first release of Konveyor with the new vision based on the Unified Experience.
- 0.2.0: June 2023 (alpha released May 2023)
- The ability to break up and plan units of work via Migration Waves is introduced
- enhancement: Migration Waves
- enhancement: Tackle Hub integration with Jira
- The ability to break up and plan units of work via Migration Waves is introduced
- 0.3.0: Planned Q3 2023 (alpha released August 2023)
- Multi-language analysis capability is introduced via analyzer-lsp that leverages Language Server Protocol.
- enhancement: Konveyor Analysis: Multi-language analyzer leveraging Language Server Protocol (LSP)
- Windup is replaced by analyzer-lsp
- Languages supported are Java and Golang.
- enhancement: Konveyor Analysis: Multi-language analyzer leveraging Language Server Protocol (LSP)
- Dynamic reporting and aggregation of analysis data across the entire application portfolio is now possible
- enhancement: Dynamic reports enhancement
- enhancement: Analyzers Report Format
- [Active development, not in 0.3.0-alpha]: New Assessment Module to replace Pathfinder
- enhancement: New assessment module enhancement
- Multi-language analysis capability is introduced via analyzer-lsp that leverages Language Server Protocol.
For more information and to get involved, please join the [email protected] mailing list and/or attend a Konveyor Community Meeting.
This roadmap is a living document and will evolve as the project progresses. Stay tuned for updates and announcements as we work together to revolutionize application modernization to Kubernetes!