Connect T4K UI hosted with HTTPS to another cluster hosted with HTTP or vice versa
This page describes MultiCloud Management through the Trilio Management console when the primary cluster's T4K UI is running on HTTPS and secondary cluster's T4K UI is on HTTP or vice versa.
Deprecated Documentation
This document is deprecated and no longer supported. For accurate, up-to-date information, please refer to the documentation for the latest version of Trilio.
# Connect T4K UI hosted with HTTPS to another cluster hosted with HTTP or vice versa
When user has two Kubernetes clusters with T4K installation and they want to connect them using T4K's Multi-Cluster Management (MCM) feature, T4K expected the UI to run on same protocol viz. HTTP
or HTTPS
.
When both clusters T4K UI instances are not running on same protocol, the browser does not allow the connection to another cluster which has T4K UI running with HTTP or vice versa. It throws an error as Blocked: Mixed Content
and the connection fails at the browser. This causes failure to add secondary cluster.
When a user want to connect the secondary Kubernetes cluster's T4K UI with primary Kubernetes cluster, as they enter the T4K UI URL in the Primary cluster's T4K UI, the Kubernetes Distribution Type
is not auto-populated. The different login options for the secondary cluster which are populated by dex are also not shown.
Please follow the below steps to resolve this issue at the browser level.
User need to allow the
Insecure Connection
to the T4K UI running on HTTP protocolClick on
Not secure
text next tohttps://
URL from where the user is accessing the T4K UI of the Primary clusterClick the option
Site Setting
From the new opened tab of
Browser Settings
, go toInsecure Content
setting and optionAllow
option from dropdown.Go to original browser tab of T4K UI of Primary cluster
Click on
Reload
, if the option toReload
is not present,Refresh
the browser tab.
Now, add the secondary cluster's T4K UI running with
HTTP
using MCM again.
Above steps should auto-populate the Kubernetes Distribution Type
and different login options to the secondary cluster using dex.
Last updated