-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Release-1.26] - Provide a means to specify that docker images from any registry should be retrieved from a given registry or the embedded registry #9687
Comments
##Environment Details Infrastructure
Node(s) CPU architecture, OS, and version: Linux 5.14.21-150500.53-default x86_64 GNU/Linux Cluster Configuration:
Config.yaml:
Reproduction
Results: Existing release behavior with embedded-registry:true / registries: "*": and K3S_P2P_ENABLE_LATEST=true all in place but there is no functionality captured by these settings yet. This is journalctl output comparison for creating a deployment using the nginx:latest image, scaling that when it's stable up to 9 replicas across all control-plane nodes in the cluster and monitoring the spegel traffic from journalctl for requests to the registry or lack thereof for this release version. $ sudo journalctl -u k3s | grep -i spegel
This journalctl output is highlighting latest images are now supported with Spegel, the registries.yaml now correctly mirrors with the wildcard "*": entry, AND does correct fallback for the server addressing another issue discovered during testing $ sudo journalctl -u k3s | grep -i latest //latest flag detection to the k3s-agent
$ sudo journalctl -u k3s | grep -i spegel
|
Backport fix for Provide a means to specify that docker images from any registry should be retrieved from a given registry or the embedded registry
The text was updated successfully, but these errors were encountered: