Prevent users from modifying addons while cluster is paused

[spowelljr]

Currently you can try enabling/disabling an addon while the cluster is paused, but it will hang. We should prevent users from doing this and notify them that they can't perform this action while the cluster is paused and they should unpause the cluster if they wish to modify the addons.

Example:

$ minikube start
$ minikube pause
$ minikube addons enable gcp-auth
# hangs

[norshtein]

/assign

[norshtein]

Hey @spowelljr , may I take this work item?

I plan to add a check whether kube-system namespace is paused in EnableOrDisableAddon, that is adding runtimePaused, err = cluster.CheckIfPaused(runner, []string{"kube-system"}) here. If paused, then raise an error. Is this correct way to fix the issue?

[swastik959]

@norshtein I tried the same way but for some reason it is not working

[spowelljr]

@norshtein I believe that should work, that seems fine to me.

[ashutosh887]

I would like to work on this @spowelljr

[spowelljr]

@ashutosh887 There is already a Pr create for this issue by @norshtein #15868

[akstron]

@spowelljr Seems like no one is working on #15868 for a long time. I would like to work on this issue, if possible.