You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,8 @@ kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and
48
48
- Applications that require rapid start-up. For e.g. an application performing real-time data processing needs to scale rapidly due to a burst in data volume.
49
49
- Serverless Functions since they need to react immediately to incoming events.
50
50
- IoT applications that run on Edge devices, because the network connectivity between the edge device and image registry would be intermittent.
51
+
- If images need to be pulled from a private registry and everyone cannot be granted access to pull images from this registry, then the images can be made available on the nodes of the cluster.
51
52
- If a cluster administrator or operator needs to roll-out upgrades to an application and wants to verify before-hand if the new images can be pulled successfully.
52
-
- If users need to use specific images in a private registry, such images can be cached in the cluster. No need to grant permissions to the registry.
0 commit comments