Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of docs: v1.6.0 requires ipc_lock cap for mlock into stable-website #17882

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #17881 to be assessed for backporting due to the inclusion of the label backport/website.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


Fixes #17780

Screenshot from 2023-07-10 11-37-29

schmichael and others added 30 commits February 27, 2023 13:49
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
….x (#16303)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…se/1.5.x (#16320)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
… into release/1.5.x (#16324)

This pull request was automerged via backport-assistant
…elease/1.5.x (#16325)

This pull request was automerged via backport-assistant
…ng into release/1.5.x (#16327)

This pull request was automerged via backport-assistant
…d showing client links/chart into release/1.5.x (#16341)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…mmand. into release/1.5.x (#16369)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…nd io respectively in the client package into release/1.5.x (#16398)

This pull request was automerged via backport-assistant
…k offerings into release/1.5.x (#16410)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
… into release/1.5.x (#17252)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…7703)

If you use `nomad node drain -force`, the drain deadline is set to -1ns. If you
have not prevented system and CSI node plugin allocations from being drained
with `-ignore-system`, they will be immediately drained as well. This is
typically not safe for CSI node plugins.

Also fix some broken links.

Fixes: #17696
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
@hashicorp-cla
Copy link

hashicorp-cla commented Jul 10, 2023

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • schmichael
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@tgross
Copy link
Member

tgross commented Jul 12, 2023

This PR is on stable-website already as part of the RC.1 release work.

@tgross tgross closed this Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants