updated error message for failing to find pods before port forward #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: sibashi <fangedhamster3114@gmail.com>
TheRealSibasishBehera
force-pushed
the
main
branch
from
4c17d57
to
01e8ae0
Compare
TheRealSibasishBehera
changed the title
nyrahul
requested changes
Jan 24, 2023
Signed-off-by: sibashi <fangedhamster3114@gmail.com>
nyrahul
approved these changes
Jan 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: sibashi fangedhamster3114@gmail.com
Error: kubearmor pod not foundNow the new error message also specifies the pod that was supposed to be found
For example in case of
karmor summaryif the client fails to find to find the podError: kubearmor discovery-engine pod not found