This message was deleted.
# generala
adamant-kite-43734
05/08/2023, 4:20 AMThis message was deleted.
l
loud-island-50549
05/08/2023, 4:56 AMI think the reason it's clear for message.
please check your IAM policy
quick start is for terraform to create single instances deploy rancher server.
So policy is for ec2.
If you create cluster by this funture .
It will create EKS cluster for you.
So I think the policy it's not the same.
I've try use AWS secrect key to create clusters with my root accounts. It's okay.
I not sure what is the minimum policy is .
But I think the funture is correct.
d
dazzling-architect-93010
05/08/2023, 5:07 AMok Thanks for the update. Is there any way I can deploy a RKE cluster using the same code?
dazzling-architect-93010
05/08/2023, 5:08 AMI mean if I provide the RKE node version in the terraform script will it deploy a RKE cluster instead of RKE2 ?
l
loud-island-50549
05/08/2023, 6:22 AMI don't know. Maybe you can try yourself.
d
dazzling-architect-93010
05/08/2023, 6:24 AMok may I know the RKE node version? which I need to provide in the tfvars file to deploy the RKE cluster instead of RKE2?
dazzling-architect-93010
05/08/2023, 10:01 AMSo what I am looking for is for RKE2 this is the value I am providing in Terraform script vars v1.24.13+rke2r1. So similarly for RKE what should be the version that I should use to deploy through this script?
h
hundreds-evening-84071
05/08/2023, 11:08 AMWith rke binary, you can run this command to get specific version:
rke config --list-version --allhundreds-evening-84071
05/08/2023, 11:09 AMand depending on version of binary you have it may have different list
hundreds-evening-84071
05/08/2023, 12:45 PMhttps://github.com/rancher/rke for RKE versions and if you review the release notes it will show you specific kubernetes versions
3 Views