Describe scenarioA clear and concise description of what your scenario is.
I followed the above link to create a single machine cluster with a linux node, and tried to add one Windows node, then get the errors below
An update is currently in progress or in an unsafe state. Please check status and complete any outstanding updates before adding another node.
Add-AksEdgeNode -JsonConfigFilePath .\ScaleConfig.json
Warning: Not able to initialize Event logger
Warning: Not able to initialize Event logger
[05/15/2024 15:32:10] *** No errors found in the add node configuration.
[05/15/2024 15:32:11] An update is currently in progress or in an unsafe state. Please check status and complete any outstanding updates before adding another node.
However, everything was seem up and running
kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 30m
kubectl get namespace
NAME STATUS AGE
aksedge Active 30m
default Active 30m
kube-node-lease Active 30m
kube-public Active 30m
kube-system Active 30m
kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ap-jkk3qye64zuc-ledge Ready control-plane 30m v1.27.6 10.10.1.2 <none> CBL-Mariner/Linux 5.15.145.2-1.cm2 containerd://1.6.26
get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-kube-controllers-7945597df9-7hj8t 1/1 Running 1 (23m ago) 30m 10.244.172.196 ap-jkk3qye64zuc-ledge <none> <none>
kube-system calico-node-r7f8r 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system calico-patch-qqlql 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system calicoctl 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system coredns-5c5c5854dd-vm9wn 1/1 Running 1 (23m ago) 30m 10.244.172.198 ap-jkk3qye64zuc-ledge <none> <none>
kube-system coredns-5c5c5854dd-zprxb 1/1 Running 1 (23m ago) 30m 10.244.172.197 ap-jkk3qye64zuc-ledge <none> <none>
kube-system etcd-ap-jkk3qye64zuc-ledge 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system kube-apiserver-ap-jkk3qye64zuc-ledge 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system kube-controller-manager-ap-jkk3qye64zuc-ledge 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system kube-proxy-q9wdz 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
kube-system kube-scheduler-ap-jkk3qye64zuc-ledge 1/1 Running 1 (23m ago) 30m 10.10.1.2 ap-jkk3qye64zuc-ledge <none> <none>
ps. I was able to create a mixed workload cluster with no issue.
Question
I am wondering what I could be doing wrong here? And any way I can check what An update is currently in progress or in an unsafe state mentions here?
Describe scenario A clear and concise description of what your scenario is. I followed the above link to create a single machine cluster with a linux node, and tried to add one Windows node, then get the errors below An update is currently in progress or in an unsafe state. Please check status and complete any outstanding updates before adding another node.
However, everything was seem up and running
ps. I was able to create a mixed workload cluster with no issue.
Question I am wondering what I could be doing wrong here? And any way I can check what
An update is currently in progress or in an unsafe statementions here?