-
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.27] - Add ability to enable "latest" image tag support for Spegel registry. #9663
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$ sudo cat /etc/systemd/system/k3s.service.env $ sudo cat /etc/rancher/k3s/registries.yaml
Results: Existing release behavior logs from journalctl scaling a deploy up across all nodes where only one node previously has the image. All nodes are embedded-registry: true pulling nginx:latest and scaling it up. $ kgp -A -o wide
$ sudo journalctl -u k3s | grep -i spegel
Explanation of journalctl logging with debug: true is essentially cluster startup at the top where system images are pulled for a bare k3s cluster. Multiple nodes join cluster as control-plane nodes. Then a single replica-count nginx:latest deployment is created and scaled across the cluster to 9 replicas. This logging is more verbose than the above because two-fold the latest images are being pulled and stored in spegel for sharing and the nodes are pulling them during scale up across the cluster. $ sudo journalctl -u k3s | grep -i spegel
|
Backport fix for Add ability to enable "latest" image tag support for Spegel registry.
The text was updated successfully, but these errors were encountered: