This message was deleted.
# developer
a
This message was deleted.
f
There is no mechanism for simultaneously talking to multiple downstream clusters. You can't just keep opening more connections, browsers have limits, etc. Fleet and MCA are designed to talk to a CRD in the one management/local cluster (and have limitations in what they do) because of this.
You could do it on the server side and present it as one response, but as you add clusters the chances of one of them responding slowly and the client having to sit a long time waiting approaches 100%
g
@full-painter-23916 I understand the implications that you point out. My question is: Is there an easier way to switch the
currentCluster
than using the
loadCluster
action?
f
I would just make one-off requests to /k8s/clusters/x/v1/pods (or something like that, on my phone and I don't work at suse anymore…) instead of trying to change the state of the store and causing it to switch the websocket and such
👍 1
And do them in parallel with a limit of like 4 at a time and a timeout for each
g
Makes sense. I was already looking at that option. Thanks for confirming. Is there an easy way to get the token that the vuex store is using to make these requests?
f
You can't get it at all, it's a httponly cookie. But you also don't need to, it will just be sent with the request
g
Is there some special way that I need to send the request to make that happen?
f
No
g
thanks so much for your help!
👍 1