Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effect of imagePullPolicy on peerd behavior and performance #63

Open
johnsonshi opened this issue Sep 12, 2024 · 0 comments
Open

Effect of imagePullPolicy on peerd behavior and performance #63

johnsonshi opened this issue Sep 12, 2024 · 0 comments

Comments

@johnsonshi
Copy link

For the community to adopt peerd, we need clarification on what happens for each of the imagePullPolicy configurations for a workload. For example, what is not clear to me is if imagePullPolicy == always, does it resolve to (1) pulling from the upstream registry or (2) pulling from fellow peers first because peerd is configured as a containerd mirror. Having this explicitly clarified would help community adoption.

For this work item to be closed, we need:

  • An architecture diagram showing the paths for each imagePullPolicy configuration and its effect on peerd (whether the image is already present on the node vs not)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant