You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion we should completely hide Monokle when the plugin is irrelevant to the end-user. Great plugins are transparent and you don't notice they are there.
And going even further, if we want to completely hide Monokle icon, we could detect if project contains any K8s resources. If not just hide all extension related UI. But then it will require a bit smarter approach to restore it when such resources are added. so it's not a quick fix.
Detecting if project is K8s related should be based on K8s manifest files present. If there are no such files Monokle icon should be hidden and all background work (like policy synchronization) paused. The only background process running, would be one checking if any K8s manifests were added.
The text was updated successfully, but these errors were encountered:
Extracted from #41:
Detecting if project is K8s related should be based on K8s manifest files present. If there are no such files Monokle icon should be hidden and all background work (like policy synchronization) paused. The only background process running, would be one checking if any K8s manifests were added.
The text was updated successfully, but these errors were encountered: