Prerequisites
Description
The inclusion and use of the NFS server as a ReadWriteMany-capable storage in the Kubernetes agent is now deprecated and will be removed in a future major version.
In v3 of the Kubernetes agent, the default storage was be changed to be a single-node ReadWriteOnce PVC.
The NFS-backed storage has unfortunately not been as reliable or performant as desired. Also, we have found customers have had significant issues with the priviledged pod requirement, especially in enterprise or highly locked-down clusters.
For v3 onwards, to get horizontally scaling pods, a custom storage class name must be provided and the default access modes changed to ReadWriteMany.
Process
- The functionality will be marked as deprecated in the
values.yaml and readme.md and defaulted to off
- After approximately 6 months the functionality will be completely removed in a major version release.
Migration Guide
See the migration guide
Prerequisites
Description
The inclusion and use of the NFS server as a
ReadWriteMany-capable storage in the Kubernetes agent is now deprecated and will be removed in a future major version.In
v3of the Kubernetes agent, the default storage was be changed to be a single-nodeReadWriteOncePVC.The NFS-backed storage has unfortunately not been as reliable or performant as desired. Also, we have found customers have had significant issues with the
priviledgedpod requirement, especially in enterprise or highly locked-down clusters.For
v3onwards, to get horizontally scaling pods, a custom storage class name must be provided and the default access modes changed toReadWriteMany.Process
values.yamlandreadme.mdand defaulted to offMigration Guide
See the migration guide