Story (Required)

Implement a mechanism to dynamically populate and update a ConfigMap that stores parent-child relationships of Kubernetes resources. This will involve listening to Kubernetes resource events and leveraging the ownerReferences }}field where applicable while handling special cases like {{Service and Endpoint relationships without ownerReferences.

Acceptance Criteria (Mandatory)

• ConfigMap Structure The ConfigMap should follow the structure below:

  apiVersion: v1
  kind: ConfigMap
  metadata:
    name: resource-relation-lookup
    namespace: argocd
  data:
    apps_Deployment: apps_ReplicaSet
    apps_ReplicaSet: core_Pod
    apps_StatefulSet: apps_ReplicaSet
    core_Service: core_Endpoint
   

   

  • Keys: Represent parent resources (e.g., apps_Deployment).
  • Values: Represent immediate child resources (e.g., apps_ReplicaSet).
• Dynamic Updates

• • The ConfigMap should be updated dynamically when:
    • A new resource is created or deleted.
    • The ownerReferences field of a resource changes.
    • Relationships like Service → Endpoint are detected based on labels or other metadata.