You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce the problem:
Create a new K8s cluster using cluster up command.
Remove K8s cluster using cluster remove command.
At this point , kube_config_cluster.yml continues to be present.
When attempting to add a new cluster using ```cluster up`` command , rke now attempts to fetch cluster state from the removed Kubernetes and it fails before it proceeds to creating a new cluster.
Sangeethas-MBP:~ sangeethahariharan1$ ./rke_darwin-amd64 cluster up
INFO[0000] Building Kubernetes cluster
INFO[0000] [ssh] Checking private key
INFO[0000] [ssh] Start tunnel for host [ip-172-31-38-78.us-east-2.compute.internal]
INFO[0000] [ssh] Start tunnel for host [ip-172-31-39-84.us-east-2.compute.internal]
INFO[0000] [ssh] Start tunnel for host [ip-172-31-37-222.us-east-2.compute.internal]
INFO[0000] [ssh] Start tunnel for host [ip-172-31-38-78.us-east-2.compute.internal]
INFO[0000] [ssh] Start tunnel for host [ip-172-31-39-84.us-east-2.compute.internal]
INFO[0000] [state] Found local kube config file, trying to get state from cluster
INFO[0000] [state] Fetching cluster state from Kubernetes
INFO[0030] Timed out waiting for kubernetes cluster to get state
INFO[0030] [certificates] Generating kubernetes certificates
INFO[0030] [certificates] Generating CA kubernetes certificates
INFO[0031] [certificates] Generating Kubernetes API server certificates
Should cluster remove , also remove kube_config_cluster.yml to indicate that rke will not be working on this cluster anymore?
The text was updated successfully, but these errors were encountered:
Tested with rke verison - v0.0.8-dev
Create a new K8s cluster using cluster up command.
Remove K8s cluster using cluster remove command.
After this , kube_config_cluster.yml get removed.
rke version v0.0.5-dev
Steps to reproduce the problem:
Create a new K8s cluster using
cluster up
command.Remove K8s cluster using
cluster remove
command.At this point , kube_config_cluster.yml continues to be present.
When attempting to add a new cluster using ```cluster up`` command , rke now attempts to fetch cluster state from the removed Kubernetes and it fails before it proceeds to creating a new cluster.
Should cluster remove , also remove kube_config_cluster.yml to indicate that rke will not be working on this cluster anymore?
The text was updated successfully, but these errors were encountered: