Closed Brianalmeida closed 2 years ago
Tested on terraform rke provider with rke updated locally to v1.3.15
Repro steps
config.tf
terraform {
required_providers {
rke = {
source = "terraform.example.com/local/rke"
version = "1.3.15"
}
}
}
# Configure RKE provider
provider "rke" {
log_file = "rke_debug.log"
}
# Create a new RKE cluster using config yaml
resource "rke_cluster" "ablender-rke" {
enable_cri_dockerd = true
kubernetes_version = "v1.24.2-rancher1-1"
nodes {
address = "<node public IP>"
internal_address = "<node private IP>"
user = "ec2-user"
role = ["etcd", "controlplane", "worker"]
}
nodes {
address = "<node public IP>"
internal_address = "<node private IP>"
user = "ec2-user"
role = ["etcd", "controlplane", "worker"]
}
services {
kubelet {
image = "rancher/hyperkube:v1.24.2-rancher1"
extra_env = ["HTTP_PROXY = http://test_proxy", "NO_PROXY = true"]
}
}
ssh_key_path = "<path to pem key file>"
}
Terraform RKE provider v1.3.4 is now released on the registry, using default image RKE v1.3.15.
@annablender Thank you
I believe we can go ahead and close this issue now.
Creating this issue to request a new RKE TF provider release to address this addon issue in RKE and make the default image the latest release of RKE (v1.3.15).