We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The MCO selects the configuration based on the selector from MachineConfigPools. MC selectors do not exists, as can be extracted from https://docs.openshift.com/container-platform/4.17/rest_api/machine_apis/machineconfigpool-machineconfiguration-openshift-io-v1.html.
Though,
intel-technology-enabling-for-openshift/machine_configuration/100-intel-iommu-on.yaml
Lines 16 to 18 in 641e777
The text was updated successfully, but these errors were encountered:
Or maybe it is easier (and more elegant) using Note Tuning Operator (https://docs.openshift.com/container-platform/4.17/scalability_and_performance/using-node-tuning-operator.html) with bootloader option on those nodes.
Sorry, something went wrong.
No branches or pull requests
The MCO selects the configuration based on the selector from MachineConfigPools. MC selectors do not exists, as can be extracted from https://docs.openshift.com/container-platform/4.17/rest_api/machine_apis/machineconfigpool-machineconfiguration-openshift-io-v1.html.
Though,
intel-technology-enabling-for-openshift/machine_configuration/100-intel-iommu-on.yaml
Lines 16 to 18 in 641e777
is not valid. For selecting only some nodes, a new MCP with the feature selectors should be created.
The text was updated successfully, but these errors were encountered: