There are several occasions where you just need to change few things in the K8s resource without really reapplying everything all over again. A good example is adding a new label or a new annotation. In the current kubectl apply method in Harness you need to know what the current k8s resource looks like before regenerating a new manifest with the changes. Kubectl patch was created specifically to address this. However harness does not have kubectl patch step. Request to add this as a step