Skip to content

Correct field_manager argument name in r/node_taint doc #2138

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 12, 2023
Merged

Correct field_manager argument name in r/node_taint doc #2138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/r/node_taint.html.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ resource "kubernetes_node_taint" "example" {
The following arguments are supported:

* `metadata` - (Required) Metadata describing which Kubernetes node to apply the taint to.
* `force_manager` - (Optional) Set the name of the field manager for the node taint.
* `field_manager` - (Optional) Set the name of the field manager for the node taint.
* `force` - (Optional) Force overwriting annotations that were created or edited outside of Terraform.
* `taint` - (Required) The taint configuration to apply to the node. For more info see [Kubernetes reference](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/).

Expand Down