ON-15464: Troubleshooting guide #123
Conversation
docs/troubleshooting.md
Outdated
| * The version of Onload compiled in the `onload-user` images and the kernel modules compiled in-cluster or out of | ||
| cluster from `onload-source` image match the standard Linux packages and are not customised variants. |
There was a problem hiding this comment.
I don't really understand what this is trying to say,
There was a problem hiding this comment.
Onload Operator v2.0 introduced a third variant of Onload: OpenOnload, EnterpriseOnload, and CloudOnload. In v3.0 we do not have such a variant and Onload's internals do not have Kubernetes- or container-related conditionals that may vary its performance. I'm open to a more precise rewording suggestion (provided it doesn't dredge up the history).
* sfnettest example now uses latency profile by default rather than recommended * Removed trailing slash on `$REGISTRY_BASE` causing invalid duplicate slashes * Added built-in syntax validation to user-modifiable commands * Documented containers of Onload Device Plugin pod * Updated README to reflect recent `setPreload` changes * Symlinks to existing docs in `docs/`
pcolledg-amd
force-pushed
the
troubleshooting
branch
from
e6d9d30 to
f4da685
Compare
docs/troubleshooting.md
Outdated
| * The version of Onload compiled in the `onload-user` images and the kernel modules compiled in-cluster or out of | ||
| cluster from `onload-source` image match the standard Linux packages and are not customised variants. |
There was a problem hiding this comment.
Onload Operator v2.0 introduced a third variant of Onload: OpenOnload, EnterpriseOnload, and CloudOnload. In v3.0 we do not have such a variant and Onload's internals do not have Kubernetes- or container-related conditionals that may vary its performance. I'm open to a more precise rewording suggestion (provided it doesn't dredge up the history).
Preview this PR's Troubleshooting Guide
$REGISTRY_BASEcausing duplicate slashes which is invalid in docker container image pathssetPreloadchangesdocs/(May further refine 'Modules and devices already loaded or mounted' and 'Day 0/1 MachineConfig' troubleshooting sections.)