ikersuen
ikersuen
I still met the same issue nowadays with latest version (helm chart 8.3.11 - bitnami redis cluster), any follow up?
Seems the merging is blocked for #284, any update for the fix?
 I also got similar error on 127.0.0.1:8897 after helm apply the kubeshark, I have port forwarded 8898 and 8899 for hub and front already.
In my case, hostPath allowPrivilegeEscalation is false by default in PodSecurityPolicy. How can I modify the values.yaml to cater this problem while the default setting for "volumes" is using hostPath...
> > Now the key is always "payload" since it simplifies the configuration. > > Agree, it's simpler. > > > but we usually reserve the right to do small...
@kyessenov I believe there should be at least a change note for reference after such critical change? I don't think changing payload structure is a "small" change that can ignore...
> We have cluster mode. Are you sure it's not just disabled in configuration? I think I found out why it don't have cluster mode. I am using valkey bitnami...
> If you want to set a value for a single chart but not all of them, should you not be using a value other than `global.`? Like `specificChart.env=dev` In...