https://rancher.com/ logo
#rke2
Title
# rke2
a

adamant-kite-43734

05/26/2022, 4:35 PM
This message was deleted.
c

creamy-pencil-82913

05/26/2022, 4:52 PM
It should only be set if you set --node-name. Are you running into some problem with that?
s

shy-zebra-53074

05/26/2022, 4:53 PM
no just working through STIG
compliance
I’ll check that node-name config
c

creamy-pencil-82913

05/26/2022, 4:54 PM
there are cases where it needs to be set in order for the cloud provider to properly find the node
seems like a weird thing to disallow
s

shy-zebra-53074

05/26/2022, 4:56 PM
yah there are several things that are odd, trying to comply exactly is the easiest otherwise they require justification and you have to go back and forth and educate the AO etc etc
c

creamy-pencil-82913

05/26/2022, 5:02 PM
hmm, actually I think at some point we started explicitly setting that in call cases in order to make sure that we’re consistently using the same hostname/node-name in all places. We do ensure that the kubelet cert has the proper entries on it regardless of what the node-name is set to, so it won’t affect the TLS verification as that text calls out.
so you might be out of luck
s

shy-zebra-53074

05/26/2022, 7:52 PM
Thanks @creamy-pencil-82913! It may be worth while to create a feature where if you set the custom arg to blank it will explicitly remove that flag, what are your thoughts? Otherwise there are no ways for users to remove any default params
3 Views