Open itmwiw opened 8 months ago
Hey there,
Sometimes, issues with machineconfigs can be related to kernel modules or configurations. Ensure that the necessary kernel modules are loaded on your FCOS nodes. Also Check if the required modules for machineconfig synchronization (such as bridge-related modules) are available. Lastly, Please Review the kernel configuration to ensure it supports the required features.
There are so many check to do, please let us know if any update on it ?
Kerem ÇELİKER Head of Cloud Architecture linkedin.com/in/keremceliker/
Its not related to machineconfig contents, just the fact that the payload contains MachineConfigs is breaking several hypershift assumptions. OKD FCOS should move towards setting initial kargs via other means instead of "update kernel arguments on pivot"
Hello, Any news regarding this issue? Thanks a lot.
OKD-SCOS was a workaround to make OKD work with Hypershift. Unlike OKD-FCOS, its installation didn't require MachineConfigs and thus didn't break Hypershift's assumptions. With OKD-SCOS currently paused, it appears there is no way to use Hypershift with OKD at the moment.
I am attempting to use Hypershift to provision an OKD cluster. I have successfully installed the OKD 'hosted cluster' up to a certain point: The Control plane's pods are 'Running,' and the node pool's VMs are provisioned, with the Nodes marked as 'Ready'. Furthermore, when I run 'oc get co,' all operators are displayed as 'AVAILABLE':
However, I still encounter an error related to the '99-okd-master-disable-mitigations' machineconfig. The exact error is as follow:
That seems OKD FCOS specific, it doesn't happen on OKD SCOS.