Add blog post: Using Finalizers to Control Deletion

[aaron-kasten]

Add block post describing operation of finalizers and owner references via kubectl delete

This blog post contains the content of a presentation given at KubeCon, in blog form.

Submission to kubenetes.io recommended by CNCF.

[k8s-ci-robot]

Welcome @aaron-kasten!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 07068ce

https://deploy-preview-26997--kubernetes-io-master-staging.netlify.app

[aaron-kasten]

@onlydole @sftim email address on git commit is that of our corporate CLA (aaron@kasten.io for a CLA for kasten.io).

I'm not sure what's missing from the PR to get the CLA detection working correctly.

edit: PS. Never mind! Looks like CLA woke up and found it.

[sftim]

Hi. “Finaliers” is misspelled, it should be Finalizers.

I've added some other feedback.

Would you be interested in turning this page into a task? For example, “Use finalizers to control deletion” could be an appropriate title.

[aaron-kasten]

@sftim thank you for the feedback! I integrated the changes - hopefully an improvement.

I went with "Using finalizers to control deletion" opposed to "Use finalizers to control deletion" - will switch to "use" if you think its a better choice.

[aaron-kasten]

@sftim what is the next step for approval? Are there any actions I need to take on this?

[sftim]

A couple more fixes needed I think. Also, would you be willing to squash the commits in this article @aaron-kasten

(if you're not sure but you're happy to have the changes combined, we can do that squashing for you).

[aaron-kasten]

@sftim:

• fixed image references (I'll know better for checking image references next time).
• shrunk images a little
• squashed local branch (appears in PR as one commit)
• merged your changes for Youtube link prologue (now gone)

I think that's it... tell me if there's anything else.

[aaron-kasten]

@sftim how does this PR look. Is it ready for merge?

[sftim]

/retitle Add blog post: Using Finalizers to Control Deletion

Review was stale

[sftim]

Preview: Using Finalizers to Control Deletion

[sftim]

We'll follow the review process or something roughly like it. At the moment the blog team is a little short on volunteers I'm afraid.

[aaron-kasten]

@sftim I understand. Tell me if there's anything I can do to help it along.

[nate-double-u]

curl -X DELETE \
  http://localhost:8080/api/v1/namespaces/default/configmaps/mymap-parent \
  -d '{ "kind":"DeleteOptions", "apiVersion":"v1", "propagationPolicy":"Background" }' \
  -H "Content-Type: application/json"

ought to work fine

Confirmed, this works. Thanks!

[aaron-kasten]

```shell
curl -X DELETE \
  http://localhost:8080/api/v1/namespaces/default/configmaps/mymap-parent \
  -d '{ "kind":"DeleteOptions", "apiVersion":"v1", "propagationPolicy":"Background" }' \
  -H "Content-Type: application/json"

ought to work fine

Confirmed, this works. Thanks!

@nate-double-u is there action I should take on this? This sounds like a layout issue?

[nate-double-u]

@nate-double-u is there action I should take on this? This sounds like a layout issue?

I think that if folks are copying and pasting snippets from the article, then @sftim's layout works better (though it may be less readable as several bits of info are put onto the same line).

I think I'd err on the side of things working for the most readers when copied from the article, so I'd suggest updating the layout. That said, this may be an issue with my setup (using zsh instead of bash), so I'd defer the decision to you and others who might have an opinion (does it work as is for other users?)

[aaron-kasten]

@nate-double-u is there action I should take on this? This sounds like a layout issue?

I think that if folks are copying and pasting snippets from the article, then @sftim's layout works better (though it may be less readable as several bits of info are put onto the same line).

I think I'd err on the side of things working for the most readers when copied from the article, so I'd suggest updating the layout. That said, this may be an issue with my setup (using zsh instead of bash), so I'd defer the decision to you and others who might have an opinion (does it work as is for other users?)

@nate-double-u agreed - I think a least-common-denominator approach is best, which is represented by keeping everything on one line. The JSON is not so large that it makes the example confusing.

[aaron-kasten]

@sftim @nate-double-u changes are in ... all set.

[nate-double-u]

new date deploy preview: Using Finalizers to Control Deletion

[nate-double-u]

I'm still not sure how to get k8s into a state described in the Forcing a Deletion of a Namespace section, but when I create a new test namespace (kubectl create namespace test) first, the snippet doesn't throw the BadRequest error.

Thanks for this @aaron-kasten, it's an interesting article!

LGTM

[aaron-kasten]

@sftim @kbhawkey unsure of what the next steps are. The PR still needs a lgtm from a reviewer.

[aaron-kasten]

@sftim is this ready?

[sftim]

I've set a publication date for Friday
/label tide/merge-method-squash

[sftim]

Echoing https://kubernetes.slack.com/archives/CJDHVD54J/p1619639542085000?thread_ts=1619639438.084800&cid=CJDHVD54J
/lgtm

My own approval
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d4fcbe65e10c806becb957553bcf3ef270fb73a6

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rolfedh, sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/blog/OWNERS [sftim]
• static/images/blog/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment