Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-6136

Investigate Using ConfigMap as a Lookup for Resource Dependencies

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • 5
    • GitOps Crimson - Sprint 3268, GitOps Crimson - Sprint 3269

      Story (Required)

      Explore the feasibility of using a ConfigMap to maintain a mapping of parent-child relationships for Kubernetes resources. The ConfigMap will have keys representing the parent resource (e.g., apps_Deployment) and values representing the immediate child (e.g., apps_ReplicaSet). The goal is to create a dependency resolution mechanism by iteratively using this lookup map until a resource with no child is found. 

      Acceptance Criteria (Mandatory)

      • Design and document the structure of the ConfigMap, including examples for common Kubernetes resource relationships.
        • Example:

       

          data:   
              apps_Deployment: apps_ReplicaSet  
              apps_ReplicaSet: core_Pod   
              apps_Statefulset: apps_ReplicaSet

       
       

      • Ensure the design accounts for dynamic resource discovery
         

      •  Resources

              rh-ee-mmeetei Mangaal Meetei
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: