You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current setup for Submariner is like this:
Control plane K8s cluster - hosts broker
Data plane K8s clusters - host agents
Over time we have had multiple control plane issues which have made us start building solutions around failing over control pane components to a new clusters instead of always trying to fix existing control plane. We generally use AKS and work with identities for cluster role based access control. However, for submariner the tokens issued to agents are using a service account as a static form of authentication.
Question: Are there recommendation on how to perform broker failovers without disrupting the service discovery model?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Our current setup for Submariner is like this:
Control plane K8s cluster - hosts broker
Data plane K8s clusters - host agents
Over time we have had multiple control plane issues which have made us start building solutions around failing over control pane components to a new clusters instead of always trying to fix existing control plane. We generally use AKS and work with identities for cluster role based access control. However, for submariner the tokens issued to agents are using a service account as a static form of authentication.
Question: Are there recommendation on how to perform broker failovers without disrupting the service discovery model?
Beta Was this translation helpful? Give feedback.
All reactions