We know there will be cases where customers require some finer grained control over their state permissions when using the standalone state transfer feature. Discussions have been ongoing during the development of 1.6.0. When we have more customers using gitops, we'll more often be hitting permission issues with files.

Two kinds of storage we've been talking about:

• Block storage. If you do not reserve scc ranges but you have your own range,
  there's a path forward to change the namespace, change the user ownership
  and the apps are still going to work
• Shared storage. Storage itself has uid/gid range and restrictions.

This is a timebox to pre-emptively try to solve these problems by exploring and exposing APIs that allow for the types of permission control that are going to be required.