⚠️ Upgrade Notes
During the upgrade, errors like the following can occur and stop the upgrade procedure:
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.kubernetes.talos_machine_configuration_apply.control_plane["<NODE>"] to include new values learned so far during apply, provider "<PROVIDER>" produced an invalid new value for .machine_configuration_hash: was
│ cty.StringVal("<OLD_HASH>"), but now cty.StringVal("<NEW_HASH>").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for module.kubernetes.talos_machine_configuration_apply.control_plane["<NODE>"] to include new values learned so far during apply, provider "<PROVIDER>" produced an invalid new value for .machine_configuration: inconsistent values for sensitive attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
This is caused by a bug in the Talos Terraform provider and should be resolved by running apply a second time. This may occur more frequently until the provider’s bug fix (siderolabs/terraform-provider-talos#359) is released, especially during Talos upgrades.
See: siderolabs/terraform-provider-talos#352
What's Changed
- chore(deps): update dependency siderolabs/talos to v1.12.9 by @renovate[bot] in #439
- chore(deps): update dependency prometheus-operator/prometheus-operator to v0.92.0 - autoclosed by @renovate[bot] in #440
- chore(deps): update actions/checkout action to v7 by @renovate[bot] in #441
- chore(deps): update helm release hcloud-cloud-controller-manager to v1.32.0 by @renovate[bot] in #438
- chore(deps): update helm release cilium to v1.18.11 by @renovate[bot] in #437
- chore(deps): update helm release hcloud-cloud-controller-manager to v1.33.0 by @renovate[bot] in #442
Full Changelog: 4.7.0...4.8.0
Contributors
renovate