Restarting Dataplane deployment shuold result in new dataplane pods to be created

[jaskeerat789]

Problem Statement

When we restart Deployment resource created by operator for a DataPlane, restarting it results in new ReplicaSet be created but controller set's it replica count to 0, thus not let the user restart DataPlane pods in a graceful manner.

Setup Information

kgo version is 1.4.2

Replication

• Install kgo
• create a dataplane
• use kubectl rollout restart deployment to restart deployment

[programmer04]

Indeed, it happens for the deployment of DataPlane and ControlPlane, it has to be fixed

[programmer04]

Could you @jaskeerat789 provide a use case for manual restart of those deployments?

[jaskeerat789]

Hey @programmer04 , Here are few scenarios that we had faced where we wanted our dataplane nodes to restart in a rolling fashion

• nodes are cordoned and we want to move dataplane nodes to another node whithout affecting traffic, this can we easily achieved if restart our dataplane deployment.
• any type of configmap/secret changes also needs dataplane to restart for them to be applied.

Let me know if there are better method to achieve above uses cases.

[jaskeerat789]

hey @programmer04, i see that is still labelled as pending author feedback. Let me know if you need further information.