Dear all, I still have the problem that our "filter by" has more than 100 operators. Tried to solve the problem yesterday with Fanis. He has set the parameter to 1000. I followed the steps Fanis described to me but still have the same result. Error message "`filter_by` has too many operations. Maximum allowed: 100. Use

--filter-by-max-ops

command line argument to customize this value." I clearly saw that the system was refreshing (see image blow) after I followed Fanis description yesterday and again this morning, but I also saw that the nodes were constantly in "unhealthy" status for a while. Any help appreciated since we are already live with the application and constantly get these errors.

Somehow that backend change has not propogated to the server. Let me update this manually for now and we will investigate and fix the root cause later today.

Okay!

@Bernhard Pertl Actually I just realized that the cluster ID beginning with

acvm...

has not yet been rotated after the backend has been added with the new limit. Did you rotate another cluster?

we have 3 clusters and I wanted to test on BUILD at first. so I did my tests on build

The cluster ID starting with

acvm...

is now fixed. You can check and confirm.

Hello Kishore, this was PROD, I did a quick test and seems to be fine. Could you also change the other 2 clusters: INTEGRATION and BUILD

Just initiated a restart for both clusters with the new filter by ops

many thanks