Users have reported a problem where attaching a cluster to certain versions of Kommander 2.X and trying to access its web endpoints results in a redirect to a bad URL, and returning "Page Not Found" errors.
You might also notice that there are incorrect URL values being overridden in ConfigMaps and Helm charts associated with traefik-forard-auth-kommander.
The most common cause for this issue is that a cluster of the same name was previously attached and detached, leaving overrides behind that are not properly cleared out.
To resolve this, you can perform the following steps, filling in the appropriate values as necessary:
1. Run `kubectl edit -n <workspace_namespace> federatedconfigmap traefik-forward-auth-kommander-overrides` and remove the entry in `spec.overrides` where `clusterName` matches the name of the attached cluster that needs to be fixed.
2. Run `kubectl edit -n <workspace_namespace> federatedconfigmap kube-oidc-proxy-overrides` and remove the cluster's entry in `spec.overrides` like in step 1.
3. Run `kubectl edit -n <workspace_namespace> kommandercluster <cluster_name>` and add any label (e.g. `foo: bar`) to `metadata.labels` in order to trigger reconciliation.
4. Check the FederatedConfigMaps edited in steps 1 and 2 to confirm that they received a fresh `spec.overrides` entry for the cluster, and that the values appear correct.
If you believe you've encountered this issue or a similar one, and the steps above are not clear, please feel free to submit a support ticket with the proper diagnostic information and we'll be happy to help:
https://support.d2iq.com/hc/en-us/articles/4408231804564