Open haliliceylan opened 1 year ago
Looks like #526 was not fixed ?
As mentioned in #526 ,
The operator failed to start because the ClusterRole assigned to the ServiceAccount was missing permissions for
redissentinels
andredisreplications
and their respective subresources/finalizers
and/status
and it is trying to watch those resources. After manually adding the resources and the respective subresources manually it started up as expected.
our prometheus alerted about this, operator is not usable per default via olm
Is there any update regarding this ?
What version of redis operator are you using?
redis-operator version: 0.15.0
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do? I just install from operatorhub with this yaml
What did you expect to see?
It should run.
What did you see instead?
A lot of errors