Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document the need for different instance names if CWA=true #835

Merged
merged 2 commits into from
Nov 21, 2024
Merged

document the need for different instance names if CWA=true #835

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9563c59
document the need for different instance names if CWA=true
jmazzitelli Nov 18, 2024
4d79f7a
Update content/en/docs/Configuration/namespace-management.md
jmazzitelli Nov 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/en/docs/Configuration/namespace-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,9 @@ As of Kiali 2.0, the following settings are no longer supported:

By default, the Kiali Server is given cluster-wide access to all namespaces on the local cluster. This is controlled by the Kiali CR setting `deployment.cluster_wide_access`, which has a default value of `true` when not specified.

For clusters that have multiple Kiali Servers installed, only one of them may be installed with `deployment.cluster_wide_access` set to `true`.
{{% alert color="info" %}}
You cannot have multiple Kiali Servers with both cluster-wide access and identical instance names. If you wish to install multiple Kiali Servers with cluster-wide access enabled, each must have a unique `deployment.instance_name` value.
{{% /alert %}}

In order to restrict the Kiali Server so that it only has access to certain namespaces on the local cluster, it must first have its cluster-wide access disabled. You do this by setting `deployment.cluster_wide_access` to `false` in the Kiali CR.

Expand Down
Loading