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
Copy file name to clipboardexpand all lines: docs/usage/namespace-offloading.md
+2
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,8 @@ The accepted values are:
44
44
***EnforceSameName**: remote namespaces are named after the local cluster's namespace.
45
45
This approach ensures **naming transparency**, which is required by certain applications, as well as guarantees that **cross-namespace DNS queries** referring to reflected services work out of the box (i.e., without adapting the target namespace name).
46
46
Yet, it can lead to **conflicts** in case a namespace with the same name already exists inside the selected remote clusters, ultimately causing the remote namespace creation request to be rejected.
47
+
***SelectedName**: you can specify the name of the remote namespace through the `--remote-namespace-name` flag.
48
+
This flag is ignored in case the *namespace mapping strategy* is set to *DefaultName* or *EnforceSameName*.
47
49
48
50
```{admonition} Note
49
51
Once configured for a given namespace, the *namespace mapping strategy* is **immutable**, and any modification is prevented by a dedicated Liqo webhook.
0 commit comments