Ciprian Hacman
Ciprian Hacman
@SohamChakraborty could you check kube-apiserver.log file for hints on the issue?
/test pull-kops-e2e-cni-cilium-ipv6
@zaneclaes It seems that there are some resources (EIPs) that stil reference the deleted NATGW. Could you delete those also and retry?
There is something that still mentions "nat-0460de55eeb540794" in logs, maybe routing table, but such references should not exist anymore. See the error message that you pasted. There is nothing in...
Yes, but kOps does not keep track of the resources. The NGW ID you see there comes from some other resource that used to reference it.
/lifecycle frozen
@ajgupta42 I am trying to reproduce this these days, but it will take some time to run the cluster. Do you still encounter such issues?
Only `etcd`, because in this case it means that `azure-sdk-for-go` fixed the issue. I updated `etcd-manager` also in the past weeks, and the fixes should be part of kOps v1.33.0-beta.1....
> I do have 2 clusters on Azure one is on kops 1.28.5 & other is 1.28.7 You might be able to use newer kOps with those k8s versions. But...
@cartermckinnon I think so, probably can be removed now. `ko` builds could also be used. Probably we should drop the Dockerfile in the future.