Search…
2.9.X
About TVK
Welcome to TrilioVault For Kubernetes (TVK)
Compatibility Matrix
Kubernetes Application Types
Features
Use Cases
Release Notes
Getting Started
Install Options
Licensing
Management Console (UI)
Trilio APIs
Uninstall Options
Architecture
Architectural Components
Backup and Restore Details
Backup Retention Process
Permissions
Resource Requirements and Limits
APIs and Command Line Reference
Operation
Operate
Observability
Management Console UI
About the UI
UI Authentication
Configuring the UI
Navigating the UI
UI How-to Guides
Performance
Configuring Resource Limits
S3 as Backup Target
Measuring Backup Performance
Ecosystem
TVK Integration with Slack using BotKube
Monitoring TVK Logs using ELK Stack
Rancher Navigation Links for TrilioVault Management Console
Optimize TVK Backups with StormForge
TVK GitHub Runner
Prometheus Metrics
AWS RDS snapshots using TVK hooks
Plugins
TVK QuickStart Plugin
TVK Preflight Checks Plugin
TVK Target Browser Plugin
TVK Log Collector Plugin
TVK Cleanup Plugin
Support
Troubleshooting Guide
Support
Appendix
Ignored Resources
OpenSource Software Disclosure
CSI Drivers
TVK Product FAQ
OpenShift OperatorHub Custom CatalogSource
Air-Gapped Install - Upstream Kubernetes
Marketplace Support
Configure OVH Object Storage as a Target
Connect TVK UI hosted with HTTPS to another cluster hosted with HTTP or vice versa
Fetch DigitalOcean Kubernetes Cluster kubeconfig for TVK UI Authentication
Force Update TVK Operator in Rancher Marketplace
Backup and Restore Virtual Machine running on OpenShift
Powered By GitBook
Connect TVK 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 TVK UI is running on HTTPS and secondary cluster's TVK UI is on HTTP or vice versa.
When user has two Kubernetes clusters with TVK installation and they want to connect them using TVK's Multi-Cluster Management (MCM) feature, TVK expected the UI to run on same protocol viz. HTTP or HTTPS.
When both clusters TVK UI instances are not running on same protocol, the browser does not allow the connection to another cluster which has TVK 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 TVK UI with primary Kubernetes cluster, as they enter the TVK UI URL in the Primary cluster's TVK 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.
  1. 1.
    User need to allow the Insecure Connection to the TVK UI running on HTTP protocol
    • Click on Not secure text next to https:// URL from where the user is accessing the TVK UI of the Primary cluster
    • Click the option Site Setting
    • From the new opened tab of Browser Settings, go to Insecure Content setting and option Allow option from dropdown.
    • Go to original browser tab of TVK UI of Primary cluster
    • Click on Reload, if the option to Reload is not present, Refresh the browser tab.
  2. 2.
    Now, add the secondary cluster's TVK 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.
Appendix - Previous
Configure OVH Object Storage as a Target
Next - Appendix
Fetch DigitalOcean Kubernetes Cluster kubeconfig for TVK UI Authentication
Last modified 1mo ago
Copy link