Andy Blendermann comments

Results 64 comments of


                                            Andy Blendermann

Provider produced inconsistent final plan, produced an invalid new value for │ .rke_config[0].machine_pools[0].cloud_credential_secret_name: was cty.StringVal(""), but now │ cty.StringVal("cattle-global-data:cc-694ng").

## Testing template #### Root cause When creating an RKE2 cluster via Terraform on any hosted provider (Amazon EC2, Azure, Linode driver so far), Terraform computes a new value for...

Provider produced inconsistent final plan, produced an invalid new value for │ .rke_config[0].machine_pools[0].cloud_credential_secret_name: was cty.StringVal(""), but now │ cty.StringVal("cattle-global-data:cc-694ng").

Blocked -- waiting on Terraform 3.0.0 for Rancher v2.7.x.

Provider produced inconsistent final plan, produced an invalid new value for │ .rke_config[0].machine_pools[0].cloud_credential_secret_name: was cty.StringVal(""), but now │ cty.StringVal("cattle-global-data:cc-694ng").

@sowmyav27 This is ready to test using Terraform rancher2 [v3.0.0-rc1](https://github.com/rancher/terraform-provider-rancher2/releases/tag/v3.0.0-rc1). Please setup local testing on the rc version of the provider with this command ``` ./setup-provider.sh rancher2 3.0.0-rc1 ```

Add token support to rancher2_user resource

Closing this PR as it's a duplicate

No support for `admission_configuration`

This is fixed in PR https://github.com/rancher/terraform-provider-rancher2/pull/1119 which updates the `admission_configuration` schema from a Type.Map to a complex type, but with state migration logic to prevent errors on upgrade.

No support for `admission_configuration`

# QA Test Template Testing with this [test plan](https://github.com/rancher/terraform-provider-rancher2/issues/1112#issuecomment-1642536486) will verify that this issue is also resolved.

ClusterRegistrationToken not being created by rancher2_cluster

@pgonin Assigning this to the Highlander team since it's a TF rke cluster on Azure. I have another community customer who is seeing this issue way back on Rancher 2.6.13....

Create new RKE-Template-Revision error. Bad response statusCode [422]. Status [422 Unprocessable Entity]

This is outdated and has been closed by the original customer who filed it.

Intermittently imports of EKS clusters never finish

@kkaempf @furkatgofurov7 Sounds great, thank you guys. For QA, post the test steps here just to be clear on how to verify the intermittent import issue is resolved.

[EKS] Support custom instance roles for node groups

@Josh-Diamond This can now be tested. on `v2.7-head` as Rancher is now referencing the correct EKS operator version https://github.com/rancher/rancher/blob/77f87c498b1517dcca5ae7fcf707dc8ebe7a95db/go.mod#L107.