- Waiting for etcd and controlplane nodes to be registered code#
- Waiting for etcd and controlplane nodes to be registered download#
The other worker nodes get stuck in "Registering" state and no additional nodes can be added using the Rancher UI, they get stuck in "IP resolved".Īll nodes are registered and I can scale up nodes through the Rancher UI. Only initial master nodes and first worker node is registered into the Kubernetes cluster. Wait for the cluster to finish building successfully Create the downstream RKE1 cluster with user addon job for creating the external load balancer waiting on condition EtcdRunningInCluster in etcd CR /cluster to be True. Add peering between Rancher virtual network and RKE1 downstream virtual network Connect to the iDRAC of a control-plane node and open the virtual console. So, logic would be that first of all, the load balancer should be created, and Rancher should actually wait/verify that it is active in the virtual network before it starts adding nodes.Īnd that is not being done, making me believe that there is a logic bug in Rancher itself. The other worker nodes get stuck in "Registering" state and any added worker node through the Rancher UI scaling feature, gets stuck in "IP Resolved" until it times out and gets deleted.
Meanwhile, the load balancer finally gets active, and any new workers don't get the load balancer as the gateway, breaking their registration. The master gets registered, and the 1st and sometimes the 2dn worker is also registered, but it is very likely that the load balancer is not active in the virtual network yet, giving the worker a gateway that works, allowing it to register.
When creating the downstream RKE cluster in Azure using node pools (1 master pool with etcd+control plane roles and 3 worker pools), the master gets created, then the load balancer is also created from the user addon. What is the role of the user logged in? Admin/Cluster
Waiting for etcd and controlplane nodes to be registered code#
See also the last Fossies "Diffs" side-by-side code changes report for "provisioner.go": 2.7.1_vs_2.7.2.ġ package clusterprovisioner 2 3 import ( 4 "context" 5 "encoding/json" 6 "fmt" 7 "net/url" 8 "path" 9 "reflect" 10 "sort" 11 "strings" 12 "time" 13 14 "/pkg/errors" 15 "/rancher/norman/controller" 16 "/rancher/norman/types/convert" 17 "/rancher/norman/types/slice" 18 "/rancher/norman/types/values" 19 apimgmtv3 "/rancher/rancher/pkg/apis//v3" 20 util "/rancher/rancher/pkg/cluster" 21 "/rancher/rancher/pkg/controllers/management/imported" 22 kd "/rancher/rancher/pkg/controllers/management/kontainerdrivermetadata" 23 "/rancher/rancher/pkg/controllers/management/secretmigrator" 24 v1 "/rancher/rancher/pkg/generated/norman/apps/v1" 25 corev1 "/rancher/rancher/pkg/generated/norman/core/v1" 26 v3 "/rancher/rancher/pkg/generated/norman//v3" 27 "/rancher/rancher/pkg/kontainer-engine/drivers/rke" 28 "/rancher/rancher/pkg/kontainer-engine/service" 29 "/rancher/rancher/pkg/kontainerdriver" 30 "/rancher/rancher/pkg/ref" 31 "/rancher/rancher/pkg/rkedialerfactory" 32 "/rancher/rancher/pkg/settings" 33 "/rancher/rancher/pkg/types/config" 34 "/rancher/rke/services" 35 rketypes "/rancher/rke/types" 36 "/sirupsen/logrus" 37 apierrors "k8s.io/apimachinery/pkg/api/errors" 38 metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" 39 "k8s.io/apimachinery/pkg/labels" 40 "k8s.io/apimachinery/pkg/runtime" 41 "k8s.io/apimachinery/pkg/util/wait" 42 "k8s.io/client-go/util/flowcontrol" 43 ) 44 45 const ( 46 RKEDriverKey = "rancherKubernetesEngineConfig" 47 KontainerEngineUpdate = "/ke-driver-update" 48 RkeRestoreAnnotation = "rke.cattle.- Cluster Type (Local/Downstream): Downstream
Waiting for etcd and controlplane nodes to be registered download#
As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) Go source code syntax highlighting (style: standard) with prefixed line numbers and code folding option.Īlternatively you can here view or download the uninterpreted source code file.
0 kommentar(er)
