This started occurring at around the same time I updated my cluster to v1.34, but I'm not sure if this is related or whether the issue is in the chart. Describe the bug After upgrading to a recent ...