Request for home, removable-media and personal-files interfaces (was: Classic confinement for wksctl)

store-requests
13

Thanks for your reply @alexmurray!

So the way I read your proposal, there’d be two different compromises to make here from our side:

  1. Switching to snap $HOME in our code / scripts
  2. Telling our users to use a different kubeconfig path (e.g. step 6 here)

While I think 1. would not be a problem, I wouldn’t like to see us doing 2. for a couple of reasons:

  • Storing kubeconfig in a wksctl subdir might seem confusing as wksctl is just a tool via which WKS Kubernetes configuration happens to be created and there is no sense I’d say in which those kubeconfigs belong to or are owned by wksctl
  • The kubeconfig file would have a different path depending on how the users would install wksctl, so we’d likely have to treat snap installs separately in our docs
  • Other tools might want to use kubeconfigs created this way and that would be made much more difficult if they were not stored somewhere at a more global level

Does that answer your question?

p.s. I discussed this with @dholbach and the use cases / permission requests for wksctl are somewhat similar to the ones for fluxctl (see Fluxctl personal-files [Was: Fluxctl snap wants to be classic]).