Add docs for credential refresh #1121
Conversation
|
|
||
| Using the output from `terraform plan`, you can make modifications to your existing Terraform config, to avoid any unwanted resource changes. For example, in the above config, adding `enable_service_links = false` to the resources would prevent any changes from occurring to the existing resources. | ||
|
|
||
| #### Known limitation: Pod data sources need manual upgrade |
There was a problem hiding this comment.
Thanks for documenting this
|
|
||
| ## Installing and testing this update | ||
|
|
||
| The `required_providers` block can be used to move between version 1.x and version 2.x of the Kubernetes provider, for testing purposes. Please note that this is only possible using `terraform plan`. Once you run `terraform apply` or `terraform refresh`, the changes to Terraform State become permanent, and rolling back is no longer an option. It may be possible to roll back the State by making a copy of `.terraform.tfstate` before running `apply` or `refresh`, but this configuration is unsupported. |
There was a problem hiding this comment.
I wonder if we should advise everyone to backup their existing state by default when preparing for the upgrade.
| $ terraform init -upgrade | ||
| ``` | ||
|
|
||
| Ensure you have a valid provider block for 2.0 before proceeding with the `terraform plan` below. In version 2.0 of the provider, [provider configuration is now required](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs). A quick way to get up and running with the new provider configuration is to set `KUBE_CONFIG_PATH` to point to your existing kubeconfig. |
There was a problem hiding this comment.
Should we explicitly mention that kubeconfig is no longer loaded by default?
Most users might no be aware of it unless they go through the changelog.
| Plan: 2 to add, 3 to change, 2 to destroy. | ||
| ``` | ||
|
|
||
| Using the output from `terraform plan`, you can make modifications to your existing Terraform config, to avoid any unwanted resource changes. For example, in the above config, adding `enable_service_links = false` to the resources would prevent any changes from occurring to the existing resources. |
There was a problem hiding this comment.
Love the spot-on example and explanation!
Update docs for 2.0 release.
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
ghost
locked as resolved and limited conversation to collaborators
4 participants
Description
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Community Note