Verifying Image Registry Origin in Private Kubernetes Clusters

[hasan4791]

Enhancement Description

• One-line enhancement description (can be used as a release note): Return image information from runtime to update pod resources, enabling users to identify and verify which registry (public or internal) an image is pulled from
  when deploying applications in private Kubernetes clusters.
• Kubernetes Enhancement Proposal: TBD
• Discussion Link: TBD
• Primary contact (assignee): @hasan4791
• Responsible SIGs:
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The proposal aims to address the challenge of verifying which registry an image is being pulled from when deploying applications in private Kubernetes clusters. Currently, users must manually check runtime logs to determine which registry was used, but this approach can be time-consuming and error-prone. The proposed solution seeks to provide transparency by adding a new label or field to the pod resource that indicates whether the image was pulled from a public or internal registry. This would help users better manage their applications' dependencies, troubleshoot issues related to image availability, and ensure compliance with organizational security policies.

[hasan4791]

/sig node