-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
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
[UX] Helm: Improved probable cause and suggested remediation #282
Comments
@Aisuko might you take this up? |
@Aisuko of course. |
Thank you, thank you. |
You are welcome, sir. Happy new year. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
//@Aisuko ^^ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go. |
Current State:
The following error message is shown in the adapter logs when deprovisioning an instance of Linkerd that was previously provisioned by Meshery (by the adapter) using
linkerd
(not using Helm).Desired State:
The probable cause and suggested remediation fields need updated with pertinent information. In this case, the error was just a warning. The uninstall using helm failed forward to uninstalling with
linkerd
binary and the overall deprovisioning operation was successful.Complete deprovisioning operation logs from adapter:
Contributor Resources
The text was updated successfully, but these errors were encountered: