Why doesn't rancher / rancher agents update the ip address in rancher management console if its changed? ( dhcp )
We do have reservations, but even so, I would like to think that w/o reservations that the agent would communicate back teh current IP address to the management console and it would be updated?
08/15/2022, 3:29 PM
don't get me started on changing the server-url and certifcates. I'm sure your issue might be somewhat related. It communicates back using DNS and your certificate should not be changed or else you will run into other issues as well. Huge failure during the Rancher acquisition IMHO and the reason I'm going to switch to other methods to maintain a central YAML repo. It certainly has helped me learn kubernetes which was one of my goals for choosing it. LOL
08/15/2022, 3:33 PM
So it would look up / change the rancher mgmt ip based on what your ip is in dns?
I was also just looking at certificates even just for the rancher management ui? which seems to be tied to agent certs also?
Then they didn't really give us a way to do through the GUI? kinda looked like we had to apply via kubectl?
08/15/2022, 3:57 PM
There are 'unsupported' ways to change the certificate search for anything from superseb. SUSE also has some 'unsupported' guidance but watch out for older helm2 vs. hellm3 info.