Closed bluebenno closed 5 years ago
Hi @bluebenno ,
Sorry that it didn't work directly as it should be.
I identified the problem: the support of --max-memory-policy
is in present in the HEAD but not docker images with the latest
tag. By default, the helm chart takes the latest
tag. But in your case, you need to overwrite this value by --set image.tag=master
.
$ helm install --name op chart/redis-operator --set image.tag=master
$ cd chart/redis-cluster
$ helm install --name mycluster . --set numberOfMaster=3 --set replicationFactor=1 --set image.tag=master
I will improve the situation by setting image.tag=master
in the charts value.yaml
files on the master branch.
Thank you for trying the redis-operator
, let me know if you have any other issue or if you have feedback to give.
thanks so much, up and running
getting
unknown flag: --max-memory-policy
on redis startup. Please say, if I have missed something or are doing something wrong.$ git clone https://github.com/AmadeusITGroup/Redis-Operator.git
$ git rev-parse HEAD
e3484d9c44af945a9953737f30dcf048b83bf9ac
$ helm install --name op chart/redis-operator
$ cd chart/redis-cluster $ helm install --name mycluster . --set numberOfMaster=3 --set replicationFactor=1
$ kubectl get pods