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
This init container thing we do right now doesn't scale well to cover the planet. It's not reasonable to have one copy of each artifact per pod when the artifacts are tens or hundreds of gigabytes. My current plan is to create a longhorn RWX volume claim and share that between all of the pods. Each pod will mount the volume claim as read-only and serve data out of it. I'll have to write a new service to manage the data that's kept in the pvc and help do the following:
download new data when it becomes available
restart the deployments as necessary when they need to start serving new data
determine when it's safe to delete old data by examining running pods
actually delete the old data once it's safe
That service will need to be able to access the cluster's api (kubelet? still getting up to speed on terminology) for items 2 and 3.
The text was updated successfully, but these errors were encountered:
This init container thing we do right now doesn't scale well to cover the planet. It's not reasonable to have one copy of each artifact per pod when the artifacts are tens or hundreds of gigabytes. My current plan is to create a longhorn RWX volume claim and share that between all of the pods. Each pod will mount the volume claim as read-only and serve data out of it. I'll have to write a new service to manage the data that's kept in the pvc and help do the following:
That service will need to be able to access the cluster's api (kubelet? still getting up to speed on terminology) for items 2 and 3.
The text was updated successfully, but these errors were encountered: