This was moved out of api/v1/helpers in kubernetes/kubernetes#46514

It's a nice convenience but not particularly complicated to implement yourself. Is there some action you'd like to take to fix this or were you just wondering why it was moved?

@timoreimann we unified the API types used by client-go with those used by the main Kubernetes in last release, so that they can share the same utility functions, but we are short-handed at the moment to finish the moving.

@ericchiang @caesarxuchao as we continue to need the function, we vendored the copy from v3. That's okay for us, though I think it'd be nicer to reference something hosted by client-go. I could imagine upstream changing the implementation in the future which would then happen detached from our copy.

If you think that bringing back AddOrUpdateTaint into client-go is a worthwhile endeavor, I'd be happy to help (though I probably won't have bandwidth available immediately). Just let me know.

We want to move all k8s-specific utility functions to k8s.io/pkg. @mengqiy do you know if we have a proposal for that?

We want to move all k8s-specific utility functions to k8s.io/pkg

I believe it will be more likely to be called k8s.io/common.
Proposal: kubernetes/kubernetes#50475
I think that repo will be ready at the very beginning of Q4.

That looks like a bigger restructuring than what I expected -- still happy to help, though it might be easier to let you (upstream) finish the migration planning first.

Shall we keep this issue open to make sure we won't forget about AddOrUpdateTaint? Or will that happen automatically once k8s.io/common shapes itself up?

I expect all the helper functions that were in pkg/api/v1/helpers.go to be move to the new repos, so it will happen "automatically". Closing.