search

rancher / terraform-provider-rke

Terraform provider plugin for deploy kubernetes cluster by RKE(Rancher Kubernetes Engine)
Mozilla Public License 2.0
340 stars 152 forks source link

Update RKE to latest #443

Closed timursaikaliev closed 8 months ago

timursaikaliev commented 9 months ago

https://github.com/rancher/rke/releases

kingnarmer commented 9 months ago

Will be good if provider updated to latest.

ajchiarello commented 9 months ago

More specifically, can we upgrade to the 1.5 branch of RKE, so that we can deploy Kubernetes 1.27+? 1.26 is EOL at the end of February 2024. https://kubernetes.io/releases/#release-v1-26

raelix commented 8 months ago

any updates on this?

enrico9034 commented 8 months ago

Sorry any update?

jiaqiluo commented 8 months ago

This can be validated with https://github.com/rancher/terraform-provider-rke/releases/tag/v1.4.4-rc1

Josh-Diamond commented 8 months ago

Ticket #443 - Test Results - ✅

Verified using tfp-rke v1.4.4-rc1:

Scenario Test Case Result
1. Using tfp-rke v1.4.4-rc1, create a standalone rke cluster w/ k8s v1.27.11-rancher1-1, ensuring cluster is active and fully functional ✅

Testing was conducted by utilizing the following main.tf file:

terraform {
  required_providers {
    rke = {
      source  = "terraform.local/local/rke"
      version = "1.4.4-rc1"
    }
    local = {
      source = "hashicorp/local"
      version = "2.4.0"
    }
  }
}

# Create a new RKE cluster using arguments
resource "rke_cluster" "rke_cluster" {
  kubernetes_version = "v1.27.11-rancher1-1"
  enable_cri_dockerd = true
  nodes {
    address = "<REDACTED>"
    internal_address = "<REDACTED>"
    user    = "ubuntu"
    role    = ["controlplane", "worker", "etcd"]
    ssh_key = file("<REDACTED>")
  }
  upgrade_strategy {
      drain = true
      max_unavailable_worker = "20%"
  }
}

# Save kubeconfig file locally
resource "local_file" "kube_config" {
  content     = "${rke_cluster.rke_cluster.kube_config_yaml}"
  filename = "<REDACTED_FILE_PATH>/kube_config.yaml"
}