daa431e385
This commit does 2 changes in the OIDC app docs: 1) The docs were updated to be explicit about the OIDC app being compatible with LDAP servers and not only with the Windows Active Directory; 2) The page "Centralized OIDC Authentication Setup for Distributed Cloud" was renamed to "Centralized vs Distributed OIDC Authentication Setup" and was moved in the index of pages to be right below the first page "Overview of LDAP Servers". The idea is to use this page as a entry point for someone learning about the OIDC app, because every user must decide between a centralized and a distributed setup and because this page has links to all other pages except "Deprovision LDAP Server Authentication". Story: 2010738 Task: 49455 Change-Id: I61c5b7f322ac8159b649c70eeaa0195d97ab12c7 Signed-off-by: Joao Victor Portal <Joao.VictorPortal@windriver.com>
1.7 KiB
1.7 KiB
Remote CLI Access
You can access the system from a remote workstation using one of the two methods.
- The first method involves using the remote
CLI (Command Line Interface)
tarball from to install a set of container-backed remote CLIs for accessing a remote . This provides access to the kubernetes-related CLIs (kubectl, helm). This approach is simple to install, portable across Linux, MacOS and Windows, and provides access to all CLIs. However, commands such as those that reference local files or require a shell are awkward to run in this environment. - The second method involves installing the
kubectl
andhelm
clients directly on the remote host. This method only provides the kubernetes-related CLIs and requires OS-specific installation instructions.
Configuring Container-backed Remote CLIs and Clients
<kubernetes-user-tutorials-configuring-container-backed-remote-clis-and-clients>
Using Container-backed Remote CLIs and Clients <using-container-based-remote-clis-and-clients>
Installing Kubectl and Helm Clients Directly on a Host <kubernetes-user-tutorials-installing-kubectl-and-helm-clients-directly-on-a-host>
Configuring Remote Helm Client <configuring-remote-helm-client>