sig-cluster-lifecycle: Standard for communicating a local registry

[nicks]

Enhancement Description

• One-line enhancement description (can be used as a release note): Standard for communicating a local registry
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR): https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry
• Primary contact (assignee): @nicks
• Responsible SIGs: sig-cluster-lifecycle
• Enhancement target (which target equals to which milestone):
  • Alpha release target (N/A)
  • Beta release target (N/A)
  • Stable release target (N/A)

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

This is a proposal for a standard way that cluster configuration tools should publicize a local registry to app-developer tools.
kubernetes-sigs/kind#1543

The proposal does not require any code changes to Kubernetes. But because it requires agreement on a common standard, sig-cluster-lifecycle suggested using the KEP process to build consensus on the proposal.

[nicks]

/sig cluster-lifeycle

[k8s-ci-robot]

@nicks: The label(s) sig/cluster-lifeycle cannot be applied, because the repository doesn't have them

In response to this:

/sig cluster-lifeycle

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nicks]

/sig cluster-lifecycle

[palnabarun]

Added the tracked/out-of-tree label after a confirming directly through Slack.