Skip to content

Commit

Permalink
Merge branch 'feat/container_service-upgrade-settings' of https://git…
Browse files Browse the repository at this point in the history
…hub.com/hqhqhqhqhqhqhqhqhqhqhq/terraform-provider-azurerm into feat/container_service-upgrade-settings
  • Loading branch information
hqhqhqhqhqhqhqhqhqhqhq committed Jan 22, 2025
2 parents a3dcc8c + d28c5e3 commit a0f05dc
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/docs/r/kubernetes_cluster.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -881,9 +881,9 @@ The `upgrade_override` block supports the following:

-> **Note:** Once set, the `upgrade_override` block cannot be removed from the configuration.

* `force_upgrade_enabled` - (Required) Whether to force upgrade the cluster. Note that this option instructs the upgrade operation to bypass upgrade protections such as checking for deprecated API usage.
* `force_upgrade_enabled` - (Required) Whether to force upgrade the cluster. Possible values are `true` or `false`.

-> **Note: Enable this option only with caution as it may render the cluster inoperative.**
!> **Important: The `force_upgrade_enabled` field instructs the upgrade operation to bypass upgrade protections (e.g. checking for deprecated API usage) which may render the cluster inoperative after the upgrade process has completed. Use the `force_upgrade_enabled` option with extreme caution only.**

* `effective_until` - (Optional) Specifies the duration, in RFC 3339 format (e.g., `2025-10-01T13:00:00Z`), the `upgrade_override` values are effective. This field must be set for the `upgrade_override` values to take effect. The date-time must be within the next 30 days.

Expand Down

0 comments on commit a0f05dc

Please sign in to comment.