This message was deleted.

Almost all right! From memory both

management

(the steve api) and

rancher

(norman api) will interact with resources in the local / upstream cluster where Rancher is installed. The

cluster

store does indeed only manage resources for the cluster in the current context. All stores will cache resources and make them available in a generic way to components. All three use an instance of the

steve

vuex store under the hood. For extensions that would need access to a cluster like store that live outside of the cluster explorer world and have a cluster context... they would need to have their own store (which would basically inherit everything from the

steve

store) and follow the standard route pattern to identify the cluster (usually something like

c-cluster...

) For extensions that don't have a cluster context though.... they would need to make make individual requests and be responsible for cacheing results. The requests could be make via the

cluster/request

action , that handles some generic things, but a url would still need to be provided and the response would need storing somewhere.

Thanks for the explanation; that clears some things up! And that

cluster/request

action was what I needed. I also found an example of what I wanted in the epinio ui repository.