[ ] Update (Add missing or refresh existing content)
[ ] Enhancement (add new site functionality)
Context
In 5.15.0 we will ship phase 1 of the federation feature which allows users to access resources across multiple clusters via the WebUI. By using the Federation API, an operator can register external clusters. A cluster does not need to be registered for the cluster that you are currently operating from (ie. self, or local-cluster), unless you want to configure the cluster name. The guide could be called something like "Multi-cluster visibility with Federation," and should contain screenshots of the context switcher in the WebUI showing how the federated views work.
ex. From local-cluster, run sensuctl create on the yaml below to register an additional cluster (same API urls as local-cluster) and define the name as us-west-2b.
This is an issue with:
Context
In 5.15.0 we will ship phase 1 of the federation feature which allows users to access resources across multiple clusters via the WebUI. By using the Federation API, an operator can register external clusters. A cluster does not need to be registered for the cluster that you are currently operating from (ie. self, or
local-cluster
), unless you want to configure the cluster name. The guide could be called something like "Multi-cluster visibility with Federation," and should contain screenshots of the context switcher in the WebUI showing how the federated views work.Asymmetric JWTs must be enabled for federation to work. See https://github.com/sensu/sensu-docs/issues/1942#issuecomment-555663228.
ex. From
local-cluster
, runsensuctl create
on the yaml below to registerus-west-2a
.ex. From
local-cluster
, runsensuctl create
on the yaml below to register an additional cluster (same API urls aslocal-cluster
) and define the name asus-west-2b
.