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
Since #381, we've known that adding
annotations: container.apparmor.security.beta.kubernetes.io/intel-qat-plugin: unconfined
for the QAT plugin daemonSet can be used to mitigate an issue where the plugin fails to initialize on an Apparmor enabled OS.
Triggered by #1571, I'm noticing the annotation setup is poorly documented so users are expected to run into the same problem
We have several ways to improve the case:
dpdkDrv
ids
The text was updated successfully, but these errors were encountered:
Let's make this annotation default. If the confugurability is needed, the annotation can be dropped with the kustomization.
Sorry, something went wrong.
I thought about making it default too but the problem is that with the operator it cannot be dropped because kustomization is not involved.
Successfully merging a pull request may close this issue.
Since #381, we've known that adding
for the QAT plugin daemonSet can be used to mitigate an issue where the plugin fails to initialize on an Apparmor enabled OS.
Triggered by #1571, I'm noticing the annotation setup is poorly documented so users are expected to run into the same problem
We have several ways to improve the case:
dpdkDrv
setup to initcontainer OR document how vfio-pci can be automatically made to probe QAT VFs (viaids
module param)The text was updated successfully, but these errors were encountered: