about liqo's usage ... #1222
-
HI, all: I have a small try: In briefly:
Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @berlinsaint, As far as I understood, you would like to spread the control-plane pods of certain components (e.g., argo) across multiple clusters, to achieve high availability. Am I correct? Liqo v0.4.0 does not support offloading pods that need to interact with the Kubernetes API server, which I believe is the reason you are getting that forbidden error. This is a feature we are planning to introduce in the next release (actually, an initial version is already merged upstream, and you can use it configuring the liqo version flag equal to the sha of the latest commit on master during the installation process), to allow offloaded pods to interact with the API server of the origin cluster (not that where it is running in that moment). As for RBACs, it would get the same privileges it would have if executed locally. Would this fit your use-case? |
Beta Was this translation helpful? Give feedback.
Hi @berlinsaint,
As far as I understood, you would like to spread the control-plane pods of certain components (e.g., argo) across multiple clusters, to achieve high availability. Am I correct?
Liqo v0.4.0 does not support offloading pods that need to interact with the Kubernetes API server, which I believe is the reason you are getting that forbidden error. This is a feature we are planning to introduce in the next release (actually, an initial version is already merged upstream, and you can use it configuring the liqo version flag equal to the sha of the latest commit on master during the installation process), to allow offloaded pods to interact with the API server of the origin cluste…