[BUG] Should we restart all pods to resync cache after vapp was updated ? about controllermesh HOT 3 OPEN

@Eikykun Yeah, that would be a serious problem. Maybe a tricky solution:

1. Return a StatusNotFound for leaderelection Get.
2. Return a mock success for leaderelection Create, but we don't really send it to apiserver. At this moment, this controller will take for it has been leader.
3. Return StatusNotAcceptable for next Get, so that controller will fail to renew and exit.

The question is controller will be leader for 1~2s in this way. I'm not sure if it is acceptable or it there some better solutions?

from controllermesh.

@Eikykun Yeah, that would be a serious problem. Maybe a tricky solution:

1. Return a StatusNotFound for leaderelection Get.
2. Return a mock success for leaderelection Create, but we don't really send it to apiserver. At this moment, this controller will take for it has been leader.
3. Return StatusNotAcceptable for next Get, so that controller will fail to renew and exit.

The question is controller will be leader for 1~2s in this way. I'm not sure if it is acceptable or it there some better solutions?

Only one pod is allowed to be leader for safety...
But all pods will be leaders in this scheme？Maybe we need to design a process to restart pods sequentially.

from controllermesh.

I'm just thinking... How about trigger the controller container restart by specific liveness probe?

When ctrlmesh webhook injects ctrlmesh-init and ctrlmesh-proxy containers into pods, it can also set the liveness probe for the original controller container. For example it checks a file in shared volume, then ctrlmesh-proxy can trigger the container to be restarted by deleting the file...

from controllermesh.