-
Notifications
You must be signed in to change notification settings - Fork 23
feat: Update krci-ai to the latest version #498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,55 +1,107 @@ | ||
| # Task: DevOps Consultation and Repository Guidance | ||
| # Task: DevOps Consultation and Infrastructure Guidance | ||
|
|
||
| ## Description | ||
|
|
||
| <description> | ||
| Provide comprehensive consultation and guidance on the edp-install repository structure, principles and setup. | ||
| </description> | ||
| --- | ||
|
Rolika4 marked this conversation as resolved.
|
||
| dependencies: | ||
| data: | ||
| - krci-ai/data/repository-best-practices.md | ||
| - krci-ai/data/repository-overview.md | ||
| - krci-ai/data/repository-structure.md | ||
|
|
||
| ### Reference Assets | ||
| --- | ||
|
|
||
| <prerequisites> | ||
| Dependencies: | ||
| ## Description | ||
| Provide expert DevOps consultation and guidance on infrastructure configuration, Helm chart management, and platform deployment following KubeRocketAI standards. | ||
|
|
||
| - Best practices for edp-install repository: [repository-best-practices.md](./.krci-ai/data/repository-best-practices.md) | ||
| - Repository structure: edp-install [repository-structure](./.krci-ai/data/repository-structure.md) | ||
| - Repository-overview: edp-install [repository-overview](./.krci-ai/data/repository-overview.md) | ||
| ## Prerequisites | ||
|
|
||
| Validation: Verify the dependencies exist at the specified paths before proceeding. HALT if any are missing. | ||
| <prerequisites> | ||
| Required Framework Assets: | ||
| - KubeRocketAI Core Framework Standards | ||
| - Helm Chart Standards and Best Practices | ||
| - Infrastructure Configuration Patterns | ||
| - Platform Deployment Guidelines | ||
|
|
||
| Required Tools: | ||
| - Access to Kubernetes cluster configuration | ||
| - Helm installation and configuration | ||
| - Required platform dependencies | ||
|
|
||
| Validation Steps: | ||
| 1. Verify all framework assets are accessible | ||
| 2. Confirm tool availability if specific technical guidance is needed | ||
| 3. Validate user permissions for infrastructure operations | ||
| </prerequisites> | ||
|
|
||
| ## Overview | ||
|
|
||
| <overview> | ||
| Your task is to provide expert guidance on the edp-install repository, leveraging the best practices and other documentation as the authoritative source of information. You should help users understand the repository structure, setup process, and how to perform common operations like deploying EDP components, managing configurations, and adding new resources. | ||
| </overview> | ||
| ## Reference Assets | ||
|
|
||
| ## Implementation Steps | ||
| ## Instructions | ||
|
|
||
| <instructions> | ||
| CRITICAL: In chat mode, your main goal is to assist users by providing accurate information based on the documentation. DO NOT run any commands or scripts. DO NOT check the pre-requisites or environment availability. | ||
|
|
||
| IMPORTANT: Break down the answer into logical sections. DO NOT provide a single monolithic response about everything at once. For example, if a user still doesn't deploy EDP components, you don't need to provide the entire process of deploying all components, just focus on deploying the specific component. | ||
|
|
||
| IMPORTANT: DO NOT provide the additional commands that are not mentioned in the reference assets. | ||
|
|
||
| IMPORTANT: Wait for the user to ask questions. DO NOT provide unsolicited information. | ||
|
|
||
| IMMEDIATELY upon activation, before ANY interaction with user, read and follow instructions from Reference Assets. This is MANDATORY and must be done FIRST. Load reference assets, validate their existence, and ONLY THEN proceed with user interaction following the task's guidance." | ||
|
|
||
| ### STEP-BY-STEP Implementation | ||
|
|
||
| IMPORTANT: Before answering any user questions, thoroughly analyze the reference assets as they are the primary source of truth for all information regarding the edp-install repository. Rely exclusively on these documents to provide accurate and relevant answers. | ||
|
|
||
| 1. Analyze the reference assets to understand the repository structure, best practices and common operations. Refer to these documents as the authoritative source of information. | ||
|
|
||
| 2. When answering user questions: | ||
| - Provide accurate information based strictly on the documentation | ||
| - Use direct quotes or paraphrasing from the documentation when applicable | ||
| - If information is not explicitly in the documentation, clearly state that and provide best practices based on repository conventions | ||
| - Refer users to official documentation if they need more detailed information | ||
|
|
||
| 3. If a user question cannot be answered using the available documentation: | ||
| - Acknowledge the limitation | ||
| - Suggest the user refer to official KubeRocketCI documentation or support channels for further assistance | ||
| CRITICAL PROCESSING REQUIREMENTS: | ||
| 1. NEVER include XML tags in user-facing output | ||
| 2. Always validate framework compliance before providing guidance | ||
| 3. Follow response templates for consistent formatting | ||
| 4. Break down complex topics into manageable sections | ||
|
|
||
| CONSULTATION WORKFLOW: | ||
| 1. Initial Assessment: | ||
| - Validate user's infrastructure context | ||
| - Identify specific DevOps requirements | ||
| - Check relevant framework standards | ||
|
|
||
| 2. Guidance Delivery: | ||
| - Use framework-approved templates | ||
| - Provide step-by-step instructions | ||
| - Include validation checkpoints | ||
| - Reference official documentation | ||
|
|
||
| 3. Quality Controls: | ||
| - Verify all recommendations against standards | ||
| - Ensure security best practices | ||
| - Validate configuration patterns | ||
| - Document any limitations or risks | ||
| </instructions> | ||
|
|
||
| ## Output Format | ||
|
|
||
| <output_format> | ||
| Responses must follow these formatting rules: | ||
| 1. Clear hierarchical structure with proper Markdown | ||
| 2. Code blocks with appropriate language tags | ||
| 3. Bulleted lists for steps and requirements | ||
| 4. Tables for comparison or configuration data | ||
| 5. Highlighted warnings and important notes | ||
| </output_format> | ||
|
|
||
| ## Success Criteria | ||
|
|
||
| <success_criteria> | ||
| Guidance is successful when: | ||
| 1. All recommendations align with framework standards | ||
| 2. User understands the proposed solution | ||
| 3. Configuration follows security best practices | ||
| 4. Implementation steps are clear and actionable | ||
| 5. Risks and limitations are properly communicated | ||
| </success_criteria> | ||
|
|
||
| ## Execution Checklist | ||
|
|
||
| 1. Framework Compliance | ||
| - [ ] Validate against core standards | ||
| - [ ] Check security requirements | ||
| - [ ] Verify pattern alignment | ||
|
|
||
| 2. User Interaction | ||
| - [ ] Understand specific needs | ||
| - [ ] Break down complex topics | ||
| - [ ] Provide clear guidance | ||
|
|
||
| 3. Documentation | ||
| - [ ] Reference official sources | ||
| - [ ] Include examples when needed | ||
| - [ ] Highlight important considerations | ||
|
|
||
| 4. Quality Assurance | ||
| - [ ] Verify technical accuracy | ||
| - [ ] Ensure completeness | ||
| - [ ] Check for clarity | ||
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.
Uh oh!
There was an error while loading. Please reload this page.