Management Console

This section describes how to configuration additional authentication mechanisms for management console

The T4K Management Console is a web UI for managing backup and restore operations across clusters. Its configuration is controlled by the TrilioVaultManager (TVM) Custom Resource, which governs ingress setup, hostname, TLS, and resource limits. Once access is configured, authentication determines who can log in and what they can do.

Access Configuration

Before users can log in, the Management Console must be exposed via ingress or port-forward:

• Configuring the UI — Set up ingress, hostname, DNS, and HTTPS access for upstream Kubernetes and OpenShift environments.

Authentication

T4K supports the following authentication methods:

• Kubeconfig Authentication

• OIDC/LDAP & OpenShift Authentication

• RBAC

If T4K has been installed at a namespace level, then a minimum of read access over the namespace is required to access the management console.

Some Kubernetes clusters may contain cloud-specific exec action or use auth-provider configuration to fetch the authentication token within the kubeconfig file. Since the binaries for the specific cloud service may not be available on the setup where the user is providing the config file, T4K may not be able to fetch the token and populate it in the kubeconfig.

To support authentication for these cloud providers, perform the steps in the following sub-pages to create a kubeconfig file with a custom kubeconfig, consisting of a service account token and cluster data.