Skip to content

🏗 Generic CR -> VR adapter #295

Open

Description

@ahmad-ibra

Summary

Develop a generic adapter for the validator framework to watch arbitrary CRs and convert them into ValidationResults.

This will allow us to instantly ingest things like Audits (internal CRs produced by tick) and K8sGPT Results, etc. We can deprecate further tick development using this approach and remove it entirely over time.

Requirements

  • Introduce a new custom resource, ValidationResultConverter & controller for same in validator core
  • Design a VRC spec to generically map arbitrary CRD fields to ValidationResult fields
  • Implement controller to reconcile VRCs, using a dynamic K8s client to continuously fetch source CRs and convert them into VRs

Activity

  1. added and removed
    enhancementEnhancement to an existing feature
    on Jul 10, 2024
  2. changed the title [-]✨ Generic CR -> VR adapter[/-] [+]🏗 Generic CR -> VR adapter[/+] on Jul 10, 2024
  3. added
    staleIssue has not had recent activity or appears to be solved. Stale issues will be automatically closed
    on Oct 9, 2024
  4. removed
    staleIssue has not had recent activity or appears to be solved. Stale issues will be automatically closed
    on Oct 16, 2024
  5. dosubot commented on Jan 20, 2025

    @dosubot

    Hi, @ahmad-ibra. I'm Dosu, and I'm helping the validator team manage their backlog. I'm marking this issue as stale.

    Issue Summary

    • You proposed creating a generic adapter to transform various Custom Resources (CRs) into ValidationResults.
    • The enhancement aims to integrate internal CRs like Audits and K8sGPT Results, potentially replacing the current tick development.
    • Key tasks include developing a new custom resource, mapping CRD fields to ValidationResult fields, and implementing a conversion controller.
    • There have been no comments or further activity on this issue.

    Next Steps

    • Please let me know if this issue is still relevant to the latest version of the validator repository by commenting here.
    • If there is no further input, this issue will be automatically closed in 7 days.

    Thank you for your understanding and contribution!

  6. added
    staleIssue has not had recent activity or appears to be solved. Stale issues will be automatically closed
    on Jan 20, 2025
  7. removed
    staleIssue has not had recent activity or appears to be solved. Stale issues will be automatically closed
    on Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions