add skip 001-spin-kube-doctor.md #2
Conversation
Signed-off-by: Rajat Jindal <[email protected]>
|
|
||
| ``` | ||
|
|
||
| #### Examples |
There was a problem hiding this comment.
A list of initial checks and how you'd envision they'd work would be helpful context here - especially for things like binary version checks where many developers might not have access to things like node debugging 😅
There was a problem hiding this comment.
You are right that depending on the user's permissions these checks may fail. maybe we can have a check to verify permissions before actually running the checks?
also added this info with current list of checks in SKIP doc.
| #------------------------------------- | ||
|
|
||
| ✓ Containerd version is supported | ||
| ✓ Containerd shim is installed and configured |
There was a problem hiding this comment.
Should we also check if the spin app itself is compatible with the shim? Say trigger type isn't supported.
There was a problem hiding this comment.
that is possible but, at this moment, these checks are not specific to any particular spin app. but seems like something that can be useful.
Signed-off-by: Rajat Jindal <[email protected]>
|
Hi @kate-goldenring @endocrimes, how do you feel about adding this to spinkube plugin? I think overtime (with support from community), this could become a useful tool for verifying common problems in spinkube setup. |
This PR adds the proposal for adding a subcommand to
spin kubeplugin.