Jarrod Johnson 6eb4bf28e5 Another iteration to try to have IP adaptive syncfiles ... It is likely that a client connects from fe80::, which is explicitly omitted from ssh principals. This time, have the client provide all currently set IP addresses and the server will make a determination. There remains the possibility it misconfigures a nic and tries to use that, inducing failure. One strategy would be to filter the addresses and only provide from the 'current' interface. Another is to just take the hit as the node is likely going to suffer a lot from such a misconfiguration anyway.		2022-10-05 12:23:47 -04:00
..
common	Fix apiclient detection of default interface	2022-09-29 13:15:37 -04:00
coreos
debian
el7	Sync up EL7 syncfileclient	2022-10-05 11:53:59 -04:00
el7-diskless	Sync up getinstalldisk and add another m.2 model	2022-09-01 13:22:50 -04:00
el8	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
el8-diskless	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
el9-diskless	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
esxi7
genesis	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
rhvh4	Sync up getinstalldisk and add another m.2 model	2022-09-01 13:22:50 -04:00
suse15	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
suse15-diskless	Set timezone on diskless boots by default	2022-08-24 16:09:05 -04:00
ubuntu20.04	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
ubuntu20.04-diskless
ubuntu22.04	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
utils	Add mechanism for copernicus to request any confluent	2022-09-02 13:32:05 -04:00
buildrpm
confluent_osdeploy.spec.tmpl