Delete statefulset - replicate kubectl delete pod blahblah --force --grace-period=0

[Daxcor69]

The odd time I have a statefulset pod that gets stuck in "Terminating" I am using the following command in node:

try {
    k8sApi = kc.makeApiClient(k8s.AppsV1Api);
    await k8sApi.deleteNamespacedStatefulSet("bob", "fvtt", undefined, undefined, 0);
  } catch (e) {}

To remove the bad pod I use:

kubectl delete pods bob-0 --grace-period=0 --force

Is there a way in this sdk, to replicate the --force behaviour?

Thanks
Brad

[brendandburns]

I'm not sure what the --force flag sends to the server, your best bet is to use kubectl --v=10 delete pods ... which will display verbose logging including all URLs and bodies sent to the server. Then you'll be able to see what needs to be specified in this client (and then you can see if this client supports it)

I think --force might actually just mean send a DELETE instead of updating the status of the pod to deleting using a PUT but I'm not certain.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten