Mention PDB updates in PodDisruptionBudget task page

[sftim]

This is a Feature Request

What would you like to be added
https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets mentions PodDisruptionBudget.

Verify that this documentation is:
- current
- correct
- relevant

Also check whether https://kubernetes.io/docs/tasks/run-application/configure-pdb/ should have any changes in light of improvements such as: kubernetes/kubernetes#69867

Revise https://kubernetes.io/docs/tasks/run-application/configure-pdb/ to mentioning how you can update a PodDisruptionBudget.

Add a section headed eg Update PDB that gives an example of how you can update the configuration of an existing PDB using kubectl.

Why is this needed
PodDisruptionBudget is slated to go GA in v1.21 and PDBs are no longer immutable.

Comments
/language en
/sig apps

[kbhawkey]

Is this issue related to issue #22391?

[sftim]

Both issues are about the same web page. This issue is about making sure the docs are ready for the PodDisruptionBudget API to graduate to stable.

[kbhawkey]

OK. Possibly address both issues in one PR.
/triage accepted

[irvifa]

/help

[k8s-ci-robot]

@irvifa:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[sladyn98]

@sftim In light of these changes kubernetes/kubernetes#69867 it would be great to add a section to this https://kubernetes.io/docs/tasks/run-application/configure-pdb/ like Update PDB and then give an example of how one can update the configuration and then hit kubectl apply which would now apply since the immutability aspect has been removed.Apart from that it looks current 👍

Furthermore https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets looks good since the configuration aspect is not mentioned anywhere in this doc that PR does not affect it. It looks to be current

[sftim]

https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets … looks to be current

Thanks, that's useful to know.

[adding a section to https://kubernetes.io/docs/tasks/run-application/configure-pdb/]

That sounds like a good idea. Thanks.

[sftim]

/retitle Mention PDB updates in PodDisruptionBudget task page

[sladyn98]

I can probably add this

[sftim]

Cool, thanks @sladyn98!

[sftim]

Relevant to #27053

[sladyn98]

@sftim #16738 Looks like this PR already added the update section, however it was added under the heading Create PDB Object which kind of cause me to miss it. So it looks good overall.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

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.