🔴 𝐈𝐦𝐩𝐫𝐨𝐯𝐢𝐬𝐢𝐧𝐠 𝐏𝐨𝐝 𝐒𝐭𝐚𝐫𝐭-𝐮𝐩 𝐭𝐢𝐦𝐞 𝐢𝐧 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐭𝐡𝐨𝐮𝐠𝐡 𝐈𝐦𝐚𝐠𝐞 𝐂𝐚𝐜𝐡𝐢𝐧𝐠
☸️ 🤔Delay in Pod startup for an application workload can be often attributed to the time taken to pull necessary
container images from the registry.
❗️ 𝑰𝒎𝒑𝒂𝒄𝒕
👉 For
#Kuberenetes clusters requiring auto-scaling, the delay in pulling a
#OCI compliant image can take a longer time, sometimes leading to network timeout (if the image pull doesn't go through the kubelet defined time-period)
👉 Further in situations where application needs to scale out horizontally or process high-speed real-time data, this may have compounding effect on the availability of the application
💥 𝑺𝒐𝒍𝒖𝒕𝒊𝒐𝒏
✅ The probable solution needs to have a cache layer on top of
#k8s, so that Kubernetes has a centralized image cache and all nodes “pull” from it
✅ To accelerate image caching, the solutions needs to sit inside
#k8s, and all nodes should have the fastest latency towards it.
A handful of #oss projects & tools helps in achieving the objective:📍 𝐇𝐚𝐫𝐛𝐨𝐫 (
https://lnkd.in/dqWZNwnh)
✍️ A pull-through proxy cache performs caching mechanism designed to optimize the distribution and retrieval of
container images within a
#container registry environment. It acts as an intermediary between clients (such as
container runtimes or build systems) and the upstream
container registry.
📍 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬-𝐢𝐦𝐚𝐠𝐞-𝐩𝐮𝐥𝐥𝐞𝐫 (
https://lnkd.in/dXXghvqt)
✍️ Deploys a huge number of
containers (one
container per image and per node / uses a daemonset for the caching mechanism), to fulfill the caching feature.
📍 𝐓𝐮𝐠𝐠𝐞𝐫 (
https://lnkd.in/dcemgYbC)
✍️ Uses a single configuration file, defined through its Helm file values. It does not allow us to segregate “system” configurations (eg : exclude specific images from the caching system) and “users” configurations
📍 𝐊𝐮𝐛𝐞-𝐢𝐦𝐚𝐠𝐞-𝐤𝐞𝐞𝐩𝐞𝐫 (𝐤𝐮𝐢𝐤) (
https://lnkd.in/dFCk9jur)
✍️ #Container image caching system for Kubernetes. It saves the
container images used by your pods in its own local registry so that these images remain available if the original becomes unavailable.
📍 𝐊𝐮𝐛𝐞-𝐟𝐥𝐞𝐝𝐠𝐞𝐝 (
https://lnkd.in/deSUwCbn)
✍️ Kubernetes add-on or operator for creating and managing a cache of
container images directly on the worker nodes of a kubernetes cluster. It allows a user to define a list of images and onto which worker nodes those images should be cached (i.e. pulled). As a result, application pods start almost instantly, since the images need not be pulled from the registry
🌐𝗙𝗼𝗹𝗹𝗼𝘄
@prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! //
Join for DevOps DOCs:
@devopsdocs 