Feat: Implement Code ingestion pipeline#162
Open
haroon0x wants to merge 4 commits intokubeflow:mainfrom
Open
Conversation
Signed-off-by: haroon0x <haroonbmc0@gmail.com>
Signed-off-by: haroon0x <haroonbmc0@gmail.com>
Signed-off-by: haroon0x <haroonbmc0@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #120
PR introduces the initial implementation of the code ingestion pipeline for the Kubeflow RAG system. The pipeline is designed to process code repositories, specifically focusing on the kubeflow/manifests repository, to provide high-fidelity context for the agentic retrieval system.
Implementation Overview
Modular Directory Structure
The ingestion logic is now organized into two distinct modules under the pipelines directory to separate documentation and code processing based on the repository structure mentioned in here
Component Architecture
The code ingestion pipeline consists of four primary stages:
Security and Robustness
Verification and Testing Results
The implementation has been verified through a complete end-to-end execution targeting the latest kubeflow/manifests repository. The results of the verification run are as follows:
Verification Execution Summary
Future Enhancements
kind,name, andcomponentfrom templates, ensuring Helm-defined resources are searchable beyond raw text.