Which resource enables data sharing between cronjobs running at various times in Kubernetes?

Which resource enables data sharing between cronjobs running at various times in Kubernetes?

• A. ConfigMap
• B. Persistent Volume
• C. Persistent Volume Claim
• D. Secret

Answer: (C)

To share data between cronjobs running at different times, you need a storage resource that multiple pods can attach to and modify. A Persistent Volume Claim provides that by requesting storage from a Persistent Volume and allowing each cronjob pod to mount the same claim. When bound, the same PVC can be mounted by all the cronjob pods, giving them a common data store that persists beyond any single job run. Using a PV alone isn’t enough, since you attach it to pods through a PVC. Also, ConfigMaps and Secrets aren’t for general data storage to be shared across workloads. Ensure the underlying storage class supports ReadWriteMany if multiple cronjobs need simultaneous access.

To share data between cronjobs running at different times, you need a storage resource that multiple pods can attach to and modify. A Persistent Volume Claim provides that by requesting storage from a Persistent Volume and allowing each cronjob pod to mount the same claim. When bound, the same PVC can be mounted by all the cronjob pods, giving them a common data store that persists beyond any single job run. Using a PV alone isn’t enough, since you attach it to pods through a PVC. Also, ConfigMaps and Secrets aren’t for general data storage to be shared across workloads. Ensure the underlying storage class supports ReadWriteMany if multiple cronjobs need simultaneous access.