Summary

During a rolling update initiated by a dynamic-plugins configuration change (via dynamic-plugin.yaml ConfigMap update) to a Backstage, users experience temporary 404 errors. This occurs because the application, which relies on PVC for caching dynamic plugins, handles traffic with inconsistent cache states across old and new pods during the transition period.

https://issues.redhat.com/browse/RHDHSUPP-290 

Goals (aka. expected user outcomes)

Solution which does not degrade user experience guaranteeing read consistency. Any pod actively serving traffic must only read from a cache that is fully populated and consistent with its current configuration version.