This message was deleted.
# rancher-desktopa
adamant-kite-43734
07/28/2023, 10:00 AMThis message was deleted.
f
flat-pizza-13361
07/28/2023, 10:02 AMIts worth noting that I run both on full k3s on its own cluster and I don't get this error it seems to be particular to rancher-desktop
r
rapid-eye-50641
07/28/2023, 3:26 PMCan you please confirm you are using the latest version 1.9.1 of Rancher Desktop.. Also, Can you please share the exact steps that lead you to the problem to help us reproduce it and investigate?
f
flat-pizza-13361
07/28/2023, 3:47 PMHi, it's version 1.9.1. Both vault and cert-manager are installed using their respective helm charts.
vault chart: 0.25.0
cert-manager chart: 1.12.3
I'm using ArgoCD to perform the install. All other pods seem to be fine.
That 10.42.0.1 address isn't from a pod or a service, which are all on 10.43.X.X, I think. I suspect this is something to do with flannel, maybe
flat-pizza-13361
07/28/2023, 3:50 PMthe
k3s-serving Copy code
Common Name: k3s
Subject Alternative Names: kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, localhost, lwh-hotapril, IP Address:10.43.0.1, IP Address:127.0.0.1, IP Address:172.25.26.23, IP Address:0:0:0:0:0:0:0:1
Organization: k3s
Organization Unit:
Locality:
State:
Country:
Valid From: July 27, 2023
Valid To: July 26, 2024
Serial Number: 4532384496416861984 (0x3ee643af966a2f20)c
calm-sugar-3169
07/31/2023, 6:49 PMIt looks as the certificate no longer matches the intended IP address, are you able to run a factory reset (that triggers generating a new set of certificates)?
27 Views