This message was deleted.
# rkea
adamant-kite-43734
10/31/2023, 10:14 AMThis message was deleted.
b
boundless-crowd-74052
10/31/2023, 11:40 AMHey Roeyb, if you want to install your first cluster with Rancher so use rke2 better use Rancher V2 because rke1 doesn't have all the options and new features like Rancher V2, I use rke1 with Terraform and now I need to reconfigure my Terraform code to use Rancher V2
https://github.com/rancher/terraform-provider-rancher2
that is my opinion maybe someone can say a different view on it.
b
bored-nest-98612
10/31/2023, 12:09 PM10X
I just finished installing rancher server 2.7.9
and I'm trying to add etcd + contorlplan nodes
and its stack on WaitingForNodeRef
on syslog i can see
Oct 31 140034 k8s-prod02-master01 rancher-system-agent[5765]: time="2023-10-31T140034+02:00" level=info msg="Rancher System Agent version v0.3.3 (9e827a5) is starting"
Oct 31 140034 k8s-prod02-master01 rancher-system-agent[5765]: time="2023-10-31T140034+02:00" level=info msg="Using directory /var/lib/rancher/agent/work for work"
Oct 31 140034 k8s-prod02-master01 rancher-system-agent[5765]: time="2023-10-31T140034+02:00" level=info msg="Starting remote watch of plans"
Oct 31 140034 k8s-prod02-master01 rancher-system-agent[5765]: E1031 140034.161618 5765 memcache.go:206] couldn't get resource list for management.cattle.io/v3:
Oct 31 140034 k8s-prod02-master01 rancher-system-agent[5765]: time="2023-10-31T140034+02:00" level=info msg="Starting /v1, Kind=Secret controller"
what is the best way to debug it ?
bored-nest-98612
10/31/2023, 12:33 PMin rancher log i see
W1031 120306.763001 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine 2023-10-31T140320.083706593+02:00 W1031 120320.083592 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster
W1031 120346.794607 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck 2023-10-31T140555.948035809+02:00 W1031 120555.947895 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet 2023-10-31T140905.398680750+02:00 W1031 120905.398467 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment 2023-10-31T140940.764687805+02:00 W1031 120940.764527 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine 2023-10-31T141002.086216777+02:00 W1031 121002.086078 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster 2023-10-31T141008.797503897+02:00 W1031 121008.797337 33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck 2023-10-31T141240.246139338+02:00 2023/10/31 121240 [INFO] [rke2configserver] fleet-default/custom-acf96780972b machineID: cfc0459b7aea21c6be744de7c5e7e6f9786fe076990f3f629d8174955aadf5e delivering planSecret custom-acf96780972b-machine-plan with token secret fleet-default/custom-acf96780972b-machine-plan-token-54wdx to system-agent 2023-10-31T141302.340274861+02:00 2023/10/31 121302 [ERROR] Error during subscribe websocket: close sent
b
boundless-crowd-74052
10/31/2023, 12:44 PMvery hard to say what exactly is wrong with your cluster and how you build it.
1- from your logs I can say that your need replace your configuration from v1alpha3 to this v1beta1
2- I can suggest you the following: when you create your cluster, include etcd and all the necessary k8s components in it, and not add them after you have already built your cluster.
3- if you use Rancher UI and trying integrate with AWS or other provider then you must apply and configure correct configuration.
b
bored-nest-98612
10/31/2023, 12:56 PMso i was able to fix it
bored-nest-98612
10/31/2023, 12:56 PMchanges tne CNI to canal
✅ 1
2 Views