Skip to content

Commit b640084

Browse files
authored
Update README.md
1 parent 9bfb204 commit b640084

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and
4848
- 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.
4949
- Serverless Functions since they need to react immediately to incoming events.
5050
- 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.
5152
- 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.
5353

5454
## Prerequisites
5555

0 commit comments

Comments
 (0)