From e236161a81dd01f5061cfeca3209d6bb69714be4 Mon Sep 17 00:00:00 2001 From: Paul Gottschling Date: Wed, 6 Jul 2022 16:30:26 -0400 Subject: [PATCH] [v10] docs: remove blocks hiding content and scope links (#14117) docs: remove blocks hiding content and scope links Backports #14085 remove blocks hiding content and scope links, fixes #14052 Co-authored-by: Alexander Klizhentas --- docs/config.json | 148 ++++-------------- .../access-controls/guides/dual-authz.mdx | 13 -- .../guides/moderated-sessions.mdx | 12 -- docs/pages/cloud/introduction.mdx | 2 +- docs/pages/enterprise/fedramp.mdx | 16 -- docs/pages/enterprise/getting-started.mdx | 15 -- docs/pages/enterprise/hsm.mdx | 10 -- docs/pages/enterprise/introduction.mdx | 2 +- docs/pages/enterprise/license.mdx | 23 --- docs/pages/enterprise/soc2.mdx | 13 -- docs/pages/enterprise/sso.mdx | 22 --- docs/pages/enterprise/sso/adfs.mdx | 22 --- docs/pages/enterprise/sso/azuread.mdx | 20 --- docs/pages/enterprise/sso/gitlab.mdx | 20 --- .../pages/enterprise/sso/google-workspace.mdx | 21 --- docs/pages/enterprise/sso/oidc.mdx | 21 --- docs/pages/enterprise/sso/okta.mdx | 20 --- docs/pages/enterprise/sso/one-login.mdx | 20 --- docs/pages/enterprise/workflow/index.mdx | 12 -- .../enterprise/workflow/resource-requests.mdx | 12 -- .../enterprise/workflow/role-requests.mdx | 12 -- docs/pages/getting-started.mdx | 6 +- docs/pages/getting-started/digitalocean.mdx | 19 --- .../getting-started/kubernetes-cluster.mdx | 28 ---- docs/pages/getting-started/linux-server.mdx | 47 ------ docs/pages/index.mdx | 6 +- docs/pages/kubernetes-access/helm/guides.mdx | 22 --- .../kubernetes-access/helm/guides/aws.mdx | 20 --- .../kubernetes-access/helm/guides/custom.mdx | 37 ----- .../helm/guides/digitalocean.mdx | 19 --- .../kubernetes-access/helm/guides/gcp.mdx | 20 --- .../helm/guides/migration.mdx | 19 --- .../guides/recording-proxy-mode.mdx | 20 --- docs/pages/setup/deployments.mdx | 21 --- .../pages/setup/deployments/aws-terraform.mdx | 51 ------ docs/pages/setup/deployments/gcp.mdx | 21 --- docs/pages/setup/deployments/ibm.mdx | 20 --- .../setup/guides/joining-nodes-aws-ec2.mdx | 20 --- docs/pages/setup/operations/scaling.mdx | 20 --- docs/pages/setup/reference/backends.mdx | 22 --- 40 files changed, 41 insertions(+), 853 deletions(-) diff --git a/docs/config.json b/docs/config.json index 0587141632475..3ce59ed210ebf 100644 --- a/docs/config.json +++ b/docs/config.json @@ -18,11 +18,7 @@ "entries": [ { "title": "Linux Server", - "slug": "/getting-started/linux-server/", - "hideInScopes": [ - "enterprise", - "cloud" - ] + "slug": "/getting-started/linux-server/" }, { "title": "Docker Compose", @@ -34,8 +30,7 @@ }, { "title": "Kubernetes Cluster", - "slug": "/getting-started/kubernetes-cluster/", - "hideInScopes": "cloud" + "slug": "/getting-started/kubernetes-cluster/" } ] }, @@ -98,22 +93,18 @@ { "title": "Deployments", "slug": "/setup/deployments/", - "hideInScopes": "cloud", "entries": [ { "title": "AWS Terraform", - "slug": "/setup/deployments/aws-terraform/", - "hideInScopes": "cloud" + "slug": "/setup/deployments/aws-terraform/" }, { "title": "GCP", - "slug": "/setup/deployments/gcp/", - "hideInScopes": "cloud" + "slug": "/setup/deployments/gcp/" }, { "title": "IBM", - "slug": "/setup/deployments/ibm/", - "hideInScopes": "cloud" + "slug": "/setup/deployments/ibm/" } ] }, @@ -123,8 +114,7 @@ "entries": [ { "title": "Scaling", - "slug": "/setup/operations/scaling/", - "hideInScopes": "cloud" + "slug": "/setup/operations/scaling/" }, { "title": "Upgrading a Cluster", @@ -180,8 +170,7 @@ }, { "title": "Joining Nodes via AWS EC2", - "slug": "/setup/guides/joining-nodes-aws-ec2/", - "hideInScopes": "cloud" + "slug": "/setup/guides/joining-nodes-aws-ec2/" }, { "title": "Using Teleport's CA with GitHub", @@ -223,8 +212,7 @@ }, { "title": "Storage Backends", - "slug": "/setup/reference/backends/", - "hideInScopes": "cloud" + "slug": "/setup/reference/backends/" }, { "title": "Networking", @@ -330,8 +318,7 @@ }, { "title": "Recording Proxy Mode", - "slug": "/server-access/guides/recording-proxy-mode/", - "hideInScopes": "cloud" + "slug": "/server-access/guides/recording-proxy-mode/" }, { "title": "BPF Session Recording", @@ -371,8 +358,7 @@ }, { "title": "Cluster", - "slug": "/kubernetes-access/getting-started/cluster/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/getting-started/cluster/" }, { "title": "Agent", @@ -405,32 +391,26 @@ { "title": "Helm Guides", "slug": "/kubernetes-access/helm/guides/", - "hideInScopes": "cloud", "entries": [ { "title": "AWS EKS Cluster", - "slug": "/kubernetes-access/helm/guides/aws/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/helm/guides/aws/" }, { "title": "Google Cloud GKE Cluster", - "slug": "/kubernetes-access/helm/guides/gcp/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/helm/guides/gcp/" }, { "title": "DigitalOcean Kubernetes Cluster", - "slug": "/kubernetes-access/helm/guides/digitalocean/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/helm/guides/digitalocean/" }, { "title": "Customize Deployment Config", - "slug": "/kubernetes-access/helm/guides/custom/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/helm/guides/custom/" }, { "title": "Migrating From Older Charts", - "slug": "/kubernetes-access/helm/guides/migration/", - "hideInScopes": "cloud" + "slug": "/kubernetes-access/helm/guides/migration/" } ] }, @@ -696,8 +676,7 @@ }, { "title": "Dual Authorization", - "slug": "/access-controls/guides/dual-authz/", - "hideInScopes": "oss" + "slug": "/access-controls/guides/dual-authz/" }, { "title": "Impersonation", @@ -705,8 +684,7 @@ }, { "title": "Moderated Sessions", - "slug": "/access-controls/guides/moderated-sessions/", - "hideInScopes": "oss" + "slug": "/access-controls/guides/moderated-sessions/" } ] }, @@ -758,123 +736,71 @@ }, { "title": "Getting Started", - "slug": "/enterprise/getting-started/", - "hideInScopes": [ - "oss", - "cloud" - ] + "slug": "/enterprise/getting-started/" }, { "title": "Single Sign-On (SSO)", "slug": "/enterprise/sso/", - "hideInScopes": [ - "oss" - ], "entries": [ { "title": "Azure Active Directory (AD)", - "slug": "/enterprise/sso/azuread/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/azuread/" }, { "title": "Active Directory (ADFS)", - "slug": "/enterprise/sso/adfs/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/adfs/" }, { "title": "Google Workspace", - "slug": "/enterprise/sso/google-workspace/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/google-workspace/" }, { "title": "GitLab", - "slug": "/enterprise/sso/gitlab/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/gitlab/" }, { "title": "OneLogin", - "slug": "/enterprise/sso/one-login/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/one-login/" }, { "title": "OIDC", - "slug": "/enterprise/sso/oidc/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/oidc/" }, { "title": "Okta", - "slug": "/enterprise/sso/okta/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/sso/okta/" } ] }, { "title": "Access Requests", "slug": "/enterprise/workflow/", - "hideInScopes": [ - "oss" - ], "entries": [ { "title": "Resource Access Requests", - "slug": "/enterprise/workflow/resource-requests/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/workflow/resource-requests/" }, { "title": "Role Access Requests", - "slug": "/enterprise/workflow/role-requests/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/workflow/role-requests/" } ] }, { "title": "FedRAMP", - "slug": "/enterprise/fedramp/", - "hideInScopes": [ - "cloud", - "oss" - ] + "slug": "/enterprise/fedramp/" }, { "title": "SOC2", - "slug": "/enterprise/soc2/", - "hideInScopes": [ - "oss" - ] + "slug": "/enterprise/soc2/" }, { "title": "HSM", - "slug": "/enterprise/hsm/", - "hideInScopes": [ - "cloud", - "oss" - ] + "slug": "/enterprise/hsm/" }, { "title": "Enterprise License File", - "slug": "/enterprise/license/", - "hideInScopes": [ - "cloud", - "oss" - ] + "slug": "/enterprise/license/" } ] }, @@ -888,11 +814,7 @@ }, { "title": "Getting Started", - "slug": "/cloud/getting-started/", - "hideInScopes": [ - "oss", - "enterprise" - ] + "slug": "/cloud/getting-started/" }, { "title": "Architecture", @@ -900,11 +822,7 @@ }, { "title": "Downloads", - "slug": "/cloud/downloads/", - "hideInScopes": [ - "oss", - "enterprise" - ] + "slug": "/cloud/downloads/" }, { "title": "FAQ", diff --git a/docs/pages/access-controls/guides/dual-authz.mdx b/docs/pages/access-controls/guides/dual-authz.mdx index 283bab9c03a1d..debc76baf44cf 100644 --- a/docs/pages/access-controls/guides/dual-authz.mdx +++ b/docs/pages/access-controls/guides/dual-authz.mdx @@ -19,19 +19,8 @@ of two team members for a privileged role `dbadmin`. edition of Teleport only supports [GitHub](../../setup/admin/github-sso.mdx) as an SSO provider. - View this guide as a user of another Teleport edition: - - - - - - - - - - The steps below describe how to use Teleport with Mattermost. You can also [integrate with many other providers](../../enterprise/workflow/index.mdx). @@ -257,5 +246,3 @@ auth_service: ``` - - \ No newline at end of file diff --git a/docs/pages/access-controls/guides/moderated-sessions.mdx b/docs/pages/access-controls/guides/moderated-sessions.mdx index c1f2ed01859f7..4acca63d91ea2 100644 --- a/docs/pages/access-controls/guides/moderated-sessions.mdx +++ b/docs/pages/access-controls/guides/moderated-sessions.mdx @@ -16,19 +16,8 @@ in the session, and terminate the session at will. Moderated Sessions requires Teleport Enterprise or Teleport Cloud. - View this guide as a user of another Teleport edition: - - - - - - - - - - ### Use cases Moderated Sessions are useful in the following scenarios: @@ -227,4 +216,3 @@ example be used to enable notifications over some external communication system. - [Moderated Sessions](https://github.com/gravitational/teleport/blob/master/rfd/0043-kubeaccess-multiparty.md) - \ No newline at end of file diff --git a/docs/pages/cloud/introduction.mdx b/docs/pages/cloud/introduction.mdx index 737cd3767ed7a..265534b50fcc3 100644 --- a/docs/pages/cloud/introduction.mdx +++ b/docs/pages/cloud/introduction.mdx @@ -33,7 +33,7 @@ desktops, and service accounts. Sign up for a free trial of Teleport Cloud - + Start using your Teleport Cloud account diff --git a/docs/pages/enterprise/fedramp.mdx b/docs/pages/enterprise/fedramp.mdx index f45b2ca153ad0..73ce2de558562 100644 --- a/docs/pages/enterprise/fedramp.mdx +++ b/docs/pages/enterprise/fedramp.mdx @@ -6,20 +6,6 @@ description: How to configure SSH, Kubernetes, database, and web app access to b Teleport provides the foundation to meet FedRAMP requirements for the purposes of accessing infrastructure. This includes support for [FIPS 140-2](https://en.wikipedia.org/wiki/FIPS\_140-2), also known as the Federal Information Processing Standard, which is the US government approved standard for cryptographic modules. This document outlines a high level overview of how Teleport FIPS mode works and how it can help your company to become FedRAMP certified. - - -This guide is intended for Teleport Enterprise users. - - - - - - - - - - - ### Obtain FedRAMP certification with Teleport Teleport includes new FedRAMP and FIPS 140-2 features to support companies that sell into @@ -158,5 +144,3 @@ is emitted to the Audit Log. - Removes all uses of non-compliant algorithms like NaCl and replace with compliant algorithms like AES-GCM. - Teleport is compiled with [BoringCrypto](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/3678) - User, host and CA certificates (and host keys for recording proxy mode) should only use 2048-bit RSA private keys. - - diff --git a/docs/pages/enterprise/getting-started.mdx b/docs/pages/enterprise/getting-started.mdx index 52d38d002048e..99b127315b3cd 100644 --- a/docs/pages/enterprise/getting-started.mdx +++ b/docs/pages/enterprise/getting-started.mdx @@ -6,20 +6,6 @@ h1: Teleport Enterprise Quick Start This guide shows you how to get up and running with Teleport Enterprise. - - -This guide is intended for Teleport Enterprise users. - - - - - - - - - - - There are three types of services Teleport can run: - **Auth Service** stores user accounts and provides authentication and @@ -474,4 +460,3 @@ If something is not working, please reach out to us by creating a ticket in your Customers who have purchased the premium support package can also ping us through your Slack channel. - diff --git a/docs/pages/enterprise/hsm.mdx b/docs/pages/enterprise/hsm.mdx index b14bbe9a72c11..2925b93d28cc2 100644 --- a/docs/pages/enterprise/hsm.mdx +++ b/docs/pages/enterprise/hsm.mdx @@ -11,16 +11,8 @@ hardware security module (HSM) to store and handle private keys. This guide is intended for Teleport Enterprise users. - - - - - - - - ## Prerequisites - Teleport v(=teleport.version=) Enterprise (self-hosted). @@ -36,7 +28,6 @@ This guide is intended for Teleport Enterprise users. Teleport Cloud and Teleport Open Source do not currently support HSM. -You can view this guide as a [Teleport Enterprise user](./hsm.mdx/?scope=enterprise). While most PKCS#11 HSMs should be supported, the Teleport team tests with AWS @@ -227,4 +218,3 @@ You are all set! Check the teleport logs for `Creating new HSM key pair` to confirm that the feature is working. You can also check that keys were created in your HSM using your HSM's admin tool. - \ No newline at end of file diff --git a/docs/pages/enterprise/introduction.mdx b/docs/pages/enterprise/introduction.mdx index 95020edf9c453..5699e0bf610f0 100644 --- a/docs/pages/enterprise/introduction.mdx +++ b/docs/pages/enterprise/introduction.mdx @@ -8,7 +8,7 @@ Teleport Enterprise is a commercial product built around Teleport's open source core. For those that want to jump right in, you can play with the -[Getting Started Guide for Teleport Enterprise](getting-started.mdx/?scope=enterprise). +[Getting Started Guide for Teleport Enterprise](getting-started.mdx). The table below gives a quick overview of the benefits of Teleport Enterprise. diff --git a/docs/pages/enterprise/license.mdx b/docs/pages/enterprise/license.mdx index 44b9ff0f33368..45c964a885882 100644 --- a/docs/pages/enterprise/license.mdx +++ b/docs/pages/enterprise/license.mdx @@ -5,27 +5,6 @@ description: Teleport enterprise license file configuration parameters and requi This guide explains the use of a license file with Teleport Enterprise. - - -This guide is intended for Teleport Enterprise users. - - - -Teleport Cloud manages licensing for customers, and there is no need to manage -license files yourself. - - - - - - - - - - - - - Commercial self-hosted Teleport subscriptions require a valid license. The license file can be downloaded from the [Teleport Customer Portal](https://dashboard.gravitational.com/web/login). When downloading the @@ -51,5 +30,3 @@ Attempts to use unlicensed products will result in an error message and users wi ```code this Teleport cluster is not licensed for database access, please contact the cluster administrator ``` - - \ No newline at end of file diff --git a/docs/pages/enterprise/soc2.mdx b/docs/pages/enterprise/soc2.mdx index 5a034ec9828e1..ced5ca3ad4c15 100644 --- a/docs/pages/enterprise/soc2.mdx +++ b/docs/pages/enterprise/soc2.mdx @@ -13,19 +13,8 @@ level overview of how Teleport can be used to help your company to become SOC2 c This guide requires Teleport Cloud or Teleport Enterprise. - View this guide as the user of another Teleport edition: - - - - - - - - - - ## Achieving SOC2 Compliance with Teleport SOC2 or Service Organization Controls were developed by the American Institute of CPAs (AICPA). They are based on five trust service areas: security, availability, processing integrity, confidentiality and privacy. @@ -93,5 +82,3 @@ Each principle has many “Points of Focus” which will apply differently to di | CC7.4 - Periodically Evaluates Incidents | Periodically, management reviews incidents related to security, availability, processing integrity, confidentiality, and privacy and identifies the need for system changes based on incident patterns and root causes. | [Use Session recording and audit logs to find patterns that lead to incidents.](../server-access/guides/bpf-session-recording.mdx) | | CC7.5 - Determines Root Cause of the Event | The root cause of the event is determined. | [Use Session recording and audit logs to find root cause.](../server-access/guides/bpf-session-recording.mdx) | | CC7.5 - Improves Response and Recovery Procedures | Lessons learned are analyzed and the incident-response plan and recovery procedures are improved. | [Replay Session recordings at your 'after action review' or postmortem meetings](../server-access/guides/bpf-session-recording.mdx) | - - diff --git a/docs/pages/enterprise/sso.mdx b/docs/pages/enterprise/sso.mdx index bd36dd414ddf5..1a433fe17c6e6 100644 --- a/docs/pages/enterprise/sso.mdx +++ b/docs/pages/enterprise/sso.mdx @@ -8,27 +8,6 @@ Users of the Enterprise edition of Teleport can log in to servers, Kubernetes clusters, databases, web applications, and Windows desktops through their organization's Single Sign-On (SSO) provider. - - - - Learn how to use Teleport's SSO integrations in Teleport Cloud. - - - Learn how to use Teleport's SSO integrations in Teleport Enterprise. - - - - - - Configure Azure Active Directory SSO for SSH, Kubernetes, databases, desktops and web apps. @@ -411,4 +390,3 @@ spec: 'env': 'dev' version: v5 ``` - diff --git a/docs/pages/enterprise/sso/adfs.mdx b/docs/pages/enterprise/sso/adfs.mdx index cf941b28de241..44bfd21d7012b 100644 --- a/docs/pages/enterprise/sso/adfs.mdx +++ b/docs/pages/enterprise/sso/adfs.mdx @@ -13,26 +13,6 @@ like: - Only members of "DBA" group can SSH into machines running PostgreSQL. - Developers must never SSH into production servers. -- ... and many others. - - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - ## Prerequisites @@ -207,5 +187,3 @@ automatically in a browser. ## Troubleshooting (!docs/pages/includes/sso/loginerrortroubleshooting.mdx!) - - diff --git a/docs/pages/enterprise/sso/azuread.mdx b/docs/pages/enterprise/sso/azuread.mdx index 62c4871a9735b..9624d9c4d34e1 100644 --- a/docs/pages/enterprise/sso/azuread.mdx +++ b/docs/pages/enterprise/sso/azuread.mdx @@ -12,25 +12,6 @@ SSH credentials to specific groups of users with a SAML Authentication Connector The following steps configure an example SAML authentication connector matching Azure AD groups with security roles. You can choose to configure other options. - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - - ## Prerequisites Before you get started you’ll need: @@ -404,4 +385,3 @@ Change the Name ID format to use email instead: ## Further reading - [Teleport Configuration Resources Reference](../../setup/reference/resources.mdx) - \ No newline at end of file diff --git a/docs/pages/enterprise/sso/gitlab.mdx b/docs/pages/enterprise/sso/gitlab.mdx index d0eb57efb2b1b..1140a2cf481e9 100644 --- a/docs/pages/enterprise/sso/gitlab.mdx +++ b/docs/pages/enterprise/sso/gitlab.mdx @@ -15,25 +15,6 @@ like: - Only members of "ProductionKubernetes" can access production Kubernetes clusters - Developers must never SSH into production servers. - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - - ## Prerequisites - At least two groups in GitLab with users assigned. @@ -201,4 +182,3 @@ automatically in a browser). (!docs/pages/includes/sso/loginerrortroubleshooting.mdx!) - \ No newline at end of file diff --git a/docs/pages/enterprise/sso/google-workspace.mdx b/docs/pages/enterprise/sso/google-workspace.mdx index 19b9410aa0c3b..be579c1dab2ff 100644 --- a/docs/pages/enterprise/sso/google-workspace.mdx +++ b/docs/pages/enterprise/sso/google-workspace.mdx @@ -12,26 +12,6 @@ to define policies like: - Only members of "DBA" Google group can SSH into machines running PostgreSQL. - Developers must never SSH into production servers. -- ... and many others. - - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - ## Prerequisites @@ -321,4 +301,3 @@ automatically in a browser). - [Google Workspace Directory API](https://developers.google.com/admin-sdk/directory) - [How nested Google Workspace groups work](https://support.google.com/a/answer/167100?hl=en) - \ No newline at end of file diff --git a/docs/pages/enterprise/sso/oidc.mdx b/docs/pages/enterprise/sso/oidc.mdx index ea29a46334946..c077b0fb7515f 100644 --- a/docs/pages/enterprise/sso/oidc.mdx +++ b/docs/pages/enterprise/sso/oidc.mdx @@ -11,26 +11,6 @@ administrators to define policies like: - Only members of "DBA" group can SSH into machines running PostgreSQL. - Developers must never SSH into production servers. -- ... and many others. - - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - ## Prerequisites @@ -259,4 +239,3 @@ identity provider if you are not automatically redirected. (!docs/pages/includes/sso/loginerrortroubleshooting.mdx!) - \ No newline at end of file diff --git a/docs/pages/enterprise/sso/okta.mdx b/docs/pages/enterprise/sso/okta.mdx index d748bab651589..3dcde77bbad49 100644 --- a/docs/pages/enterprise/sso/okta.mdx +++ b/docs/pages/enterprise/sso/okta.mdx @@ -15,25 +15,6 @@ like: - Only members of "DBA" group can SSH into machines running PostgreSQL. - Developers must never SSH into production servers. - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - - ## Prerequisites - Okta account with admin access. Your account must include users and at least two groups. @@ -191,4 +172,3 @@ automatically in a browser). (!docs/pages/includes/sso/loginerrortroubleshooting.mdx!) - \ No newline at end of file diff --git a/docs/pages/enterprise/sso/one-login.mdx b/docs/pages/enterprise/sso/one-login.mdx index d5deb6fc282a2..6892c427b5088 100644 --- a/docs/pages/enterprise/sso/one-login.mdx +++ b/docs/pages/enterprise/sso/one-login.mdx @@ -13,25 +13,6 @@ like: - Developers must never SSH into production servers. - ... and many others. - - - This guide requires Teleport Cloud or Teleport Enterprise. - - View this guide as the user of another Teleport edition: - - - - - - - - - - - - ## Prerequisites - One Login account with admin access and users assigned to at least two groups. @@ -195,4 +176,3 @@ automatically in a browser). (!docs/pages/includes/sso/loginerrortroubleshooting.mdx!) - \ No newline at end of file diff --git a/docs/pages/enterprise/workflow/index.mdx b/docs/pages/enterprise/workflow/index.mdx index 6830e637101cf..6ad0cff893138 100644 --- a/docs/pages/enterprise/workflow/index.mdx +++ b/docs/pages/enterprise/workflow/index.mdx @@ -16,19 +16,8 @@ requesting a role via the Teleport CLI. Full access request functionality, including Resource Access Requests and an intuitive and searchable UI are available in Teleport Enterprise. -View this guide as the user of another Teleport edition: - - - - - - - - - - ## Resource Access Requests Resource Access Requests follow the principle of least privilege. On teams @@ -49,4 +38,3 @@ system-wide tasks. ## Integrating with an External Tool (!docs/pages/includes/access-request-integrations.mdx!) - diff --git a/docs/pages/enterprise/workflow/resource-requests.mdx b/docs/pages/enterprise/workflow/resource-requests.mdx index 475e53ec13cb2..b94d7ebe30118 100644 --- a/docs/pages/enterprise/workflow/resource-requests.mdx +++ b/docs/pages/enterprise/workflow/resource-requests.mdx @@ -18,19 +18,8 @@ requesting a role via the Teleport CLI. Full access request functionality, including Resource Access Requests and an intuitive and searchable UI are available in Teleport Enterprise. -View this guide as the user of another Teleport edition: - - - - - - - - - - ## Prerequisites (!docs/pages/includes/commercial-prereqs-tabs.mdx!) @@ -362,4 +351,3 @@ resources accessible by the `staging-access` role. ### Integrating with an External Tool (!docs/pages/includes/access-request-integrations.mdx!) - diff --git a/docs/pages/enterprise/workflow/role-requests.mdx b/docs/pages/enterprise/workflow/role-requests.mdx index 6c184b9540f4c..b88a3da1df0e9 100644 --- a/docs/pages/enterprise/workflow/role-requests.mdx +++ b/docs/pages/enterprise/workflow/role-requests.mdx @@ -16,19 +16,8 @@ requesting a role via the Teleport CLI. Full access request functionality, including Resource Access Requests and an intuitive and searchable UI are available in Teleport Enterprise. -View this guide as the user of another Teleport edition: - - - - - - - - - - ## Prerequisites (!docs/pages/includes/commercial-prereqs-tabs.mdx!) @@ -275,4 +264,3 @@ $ tctl request approve --roles=role-1,role-3 --reason='Approved, but not role-2 ## Integrating with an External Tool (!docs/pages/includes/access-request-integrations.mdx!) - diff --git a/docs/pages/getting-started.mdx b/docs/pages/getting-started.mdx index 2bcf846fb2702..76467f82b1aef 100644 --- a/docs/pages/getting-started.mdx +++ b/docs/pages/getting-started.mdx @@ -33,7 +33,7 @@ Host your own Teleport deployment. Learn how to host your own open source Teleport deployment on a standalone @@ -43,7 +43,7 @@ Host your own Teleport deployment. Use our DigitalOcean 1-Click App to quickly spin up Teleport on a droplet. @@ -52,7 +52,7 @@ Host your own Teleport deployment. Learn how to host your own open source Teleport deployment on Kubernetes. diff --git a/docs/pages/getting-started/digitalocean.mdx b/docs/pages/getting-started/digitalocean.mdx index d2eb4314c5270..8ba798db477cd 100644 --- a/docs/pages/getting-started/digitalocean.mdx +++ b/docs/pages/getting-started/digitalocean.mdx @@ -7,23 +7,6 @@ videoBanner: voHQlSX_czE This tutorial will guide you through quickly getting started with Teleport on DigitalOcean with the Teleport 1-Click Droplet app. - - -This guide is intended for users of Teleport Open Source. - - - - - - - - - - If you are looking for a manual installation, refer to our [Linux installation guide](./linux-server.mdx). @@ -134,5 +117,3 @@ You can also secure access to databases, DigitalOcean Marketplace apps, and Kube Secure access to Windows Server. - - \ No newline at end of file diff --git a/docs/pages/getting-started/kubernetes-cluster.mdx b/docs/pages/getting-started/kubernetes-cluster.mdx index 3ac58b455a52c..e78cb7eb8c658 100644 --- a/docs/pages/getting-started/kubernetes-cluster.mdx +++ b/docs/pages/getting-started/kubernetes-cluster.mdx @@ -8,35 +8,8 @@ This guide shows you how to deploy the Teleport Auth Service and Proxy Service o Instead, Teleport Cloud users should consult the following guide, which shows you how to connect a Teleport Kubernetes Service agent to an existing Teleport cluster: - - - - - -You can also view this guide as a user of another Teleport edition: - - - - - - - - - Teleport can provide secure, unified access to your Kubernetes clusters. This guide will show you how to: - Deploy Teleport in a Kubernetes cluster. @@ -377,4 +350,3 @@ the default one in case there is a problem. - [Federated Access using Trusted Clusters](../kubernetes-access/guides/federation.mdx) - [Single-Sign On and Kubernetes Access Control](../kubernetes-access/controls.mdx) - diff --git a/docs/pages/getting-started/linux-server.mdx b/docs/pages/getting-started/linux-server.mdx index d65cb5c46e26f..75a001f04cbc1 100644 --- a/docs/pages/getting-started/linux-server.mdx +++ b/docs/pages/getting-started/linux-server.mdx @@ -8,52 +8,6 @@ This tutorial will guide you through the steps needed to install and run Teleport (=teleport.version=) on a Linux machine, then show you how to use Teleport to configure access to resources. - - -This guide is intended for users of the self-hosted, Open Source edition of -Teleport. - - - - - - - - - - - - -This guide is intended for users of the self-hosted, Open Source edition of -Teleport. - - - - - - - - - - - - We will run the following Teleport services: - **Teleport Auth Service:** The certificate authority for your cluster. It @@ -412,4 +366,3 @@ Teleport tasks, such as: - How Let's Encrypt uses the [ACME protocol](https://letsencrypt.org/how-it-works/) to issue certificates - \ No newline at end of file diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx index 7f5812d26323e..ac4c799027263 100644 --- a/docs/pages/index.mdx +++ b/docs/pages/index.mdx @@ -42,7 +42,7 @@ You can also [compare Teleport editions](faq.mdx#how-is-open-source-different-fr Learn how to host your own open source Teleport deployment on a standalone @@ -52,7 +52,7 @@ You can also [compare Teleport editions](faq.mdx#how-is-open-source-different-fr Get started with a self-hosted Teleport Enterprise deployment, which gives you @@ -60,7 +60,7 @@ You can also [compare Teleport editions](faq.mdx#how-is-open-source-different-fr - + Try Teleport hosted by us in the cloud for free. diff --git a/docs/pages/kubernetes-access/helm/guides.mdx b/docs/pages/kubernetes-access/helm/guides.mdx index 031b27a2af797..150a091fbe813 100644 --- a/docs/pages/kubernetes-access/helm/guides.mdx +++ b/docs/pages/kubernetes-access/helm/guides.mdx @@ -9,7 +9,6 @@ layout: tocless-doc These guides show you how to set up a full self-hosted Teleport deployment using our `teleport-cluster` Helm chart. - Getting started with Kubernetes Access @@ -24,25 +23,6 @@ our `teleport-cluster` Helm chart. Running a Teleport cluster in Kubernetes with a custom Teleport config - - - - - Learn how to deploy an open source Teleport cluster using Helm. - - - Learn how to deploy a Teleport Enterprise cluster using Helm. - - - ## Detailed Helm chart references @@ -59,7 +39,6 @@ Deploy the Teleport Kubernetes Service, Application Service, or Database Service - ## Migration Guides @@ -72,4 +51,3 @@ icon="kubernetes" - \ No newline at end of file diff --git a/docs/pages/kubernetes-access/helm/guides/aws.mdx b/docs/pages/kubernetes-access/helm/guides/aws.mdx index a36a073dfe5e8..89840af86b124 100644 --- a/docs/pages/kubernetes-access/helm/guides/aws.mdx +++ b/docs/pages/kubernetes-access/helm/guides/aws.mdx @@ -10,27 +10,8 @@ using Teleport Helm charts and AWS products (DynamoDB and S3). (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-cloud-warning.mdx!) -You can also view this guide as a user of another Teleport edition: - - - - - - - - - - ## Prerequisites (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-prereqs.mdx!) @@ -557,4 +538,3 @@ See the [high availability section of our Helm chart reference](../reference/tel Read the [`cert-manager` documentation](https://cert-manager.io/docs/). - \ No newline at end of file diff --git a/docs/pages/kubernetes-access/helm/guides/custom.mdx b/docs/pages/kubernetes-access/helm/guides/custom.mdx index 05cc327c2c7bd..6db9424517ffc 100644 --- a/docs/pages/kubernetes-access/helm/guides/custom.mdx +++ b/docs/pages/kubernetes-access/helm/guides/custom.mdx @@ -9,41 +9,6 @@ config file using Teleport Helm charts. This setup can be useful when you already have an existing Teleport cluster and would like to start running it in Kubernetes, or when migrating your setup from a legacy version of the Helm charts. - - -Teleport Cloud users should consult the following guide, which shows -you how to connect a Teleport Kubernetes Service agent to an existing Teleport -cluster: - - - - - - -You can also view this guide as a user of another Teleport edition: - - - - - - - - - - - ## Prerequisites (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-prereqs.mdx!) @@ -273,5 +238,3 @@ $ helm --namespace teleport uninstall teleport You can follow our [Getting Started with Teleport guide](../../../setup/guides/docker.mdx#step-34-creating-a-teleport-user) to finish setting up your Teleport cluster. - - diff --git a/docs/pages/kubernetes-access/helm/guides/digitalocean.mdx b/docs/pages/kubernetes-access/helm/guides/digitalocean.mdx index ee0da75a4958f..de2577463ef18 100644 --- a/docs/pages/kubernetes-access/helm/guides/digitalocean.mdx +++ b/docs/pages/kubernetes-access/helm/guides/digitalocean.mdx @@ -22,25 +22,8 @@ icon="kubernetes" -You can also view this guide as a user of another Teleport edition: - - - - - - - - This guide will show you how to get started with Teleport on DigitalOcean Kubernetes. @@ -228,5 +211,3 @@ Teleport keeps an audit log of access to a Kubernetes cluster. In the screenshot - [Setup CI/CD Access with Teleport](../../guides/cicd.mdx) - [Federated Access using Trusted Clusters](../../guides/federation.mdx) - [Single-Sign On and Kubernetes Access Control](../../controls.mdx) - - \ No newline at end of file diff --git a/docs/pages/kubernetes-access/helm/guides/gcp.mdx b/docs/pages/kubernetes-access/helm/guides/gcp.mdx index d00808545e609..5bf765307fcd8 100644 --- a/docs/pages/kubernetes-access/helm/guides/gcp.mdx +++ b/docs/pages/kubernetes-access/helm/guides/gcp.mdx @@ -10,27 +10,8 @@ using Teleport Helm charts and Google Cloud Platform products (Firestore and Goo (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-cloud-warning.mdx!) -You can also view this guide as a user of another Teleport edition: - - - - - - - - - - ## Prerequisites (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-prereqs.mdx!) @@ -488,4 +469,3 @@ Teleport cluster. See the [high availability section of our Helm chart reference](../reference/teleport-cluster.mdx#highavailability) for more details on high availability. - \ No newline at end of file diff --git a/docs/pages/kubernetes-access/helm/guides/migration.mdx b/docs/pages/kubernetes-access/helm/guides/migration.mdx index 53c9c934daa20..790dbcaa7a52e 100644 --- a/docs/pages/kubernetes-access/helm/guides/migration.mdx +++ b/docs/pages/kubernetes-access/helm/guides/migration.mdx @@ -19,25 +19,8 @@ to use the newer `teleport-cluster` Helm chart instead. You can also view this guide as a user of another Teleport edition: - - - - - - - - - ## Prerequisites (!docs/pages/kubernetes-access/helm/includes/teleport-cluster-prereqs.mdx!) @@ -270,5 +253,3 @@ To uninstall the `teleport-cluster` chart, use `helm uninstall `. ```code $ helm --namespace teleport-cluster uninstall teleport ``` - - \ No newline at end of file diff --git a/docs/pages/server-access/guides/recording-proxy-mode.mdx b/docs/pages/server-access/guides/recording-proxy-mode.mdx index d7c4baa735503..99c6812d23fad 100644 --- a/docs/pages/server-access/guides/recording-proxy-mode.mdx +++ b/docs/pages/server-access/guides/recording-proxy-mode.mdx @@ -23,27 +23,8 @@ interested in setting up session recording, read our [Server Access Getting Started Guide](../getting-started.mdx) so you can start replacing your OpenSSH servers with Teleport Nodes. -You can also view this guide as a user of another Teleport edition: - - - - - - - - - - We consider Recording Proxy Mode to be less secure than recording at the Node level for two reasons: @@ -271,4 +252,3 @@ dropped. To increase the concurrency level, increase the value to something like `MaxStartups 50:30:100`. This allows 50 concurrent connections and a max of 100. - \ No newline at end of file diff --git a/docs/pages/setup/deployments.mdx b/docs/pages/setup/deployments.mdx index d23e6a49228f7..84aa25cf463e2 100644 --- a/docs/pages/setup/deployments.mdx +++ b/docs/pages/setup/deployments.mdx @@ -7,26 +7,6 @@ layout: tocless-doc These guides show you how to set up a full self-hosted Teleport deployment on the platform of your choice. - - - - View our deployment guides as an Open Source Teleport user. - - - View our deployment guides as a Teleport Enterprise user. - - - - -
  • [AWS Terraform](./deployments/aws-terraform.mdx). Deploy HA Teleport with Terraform Provider on AWS. @@ -38,4 +18,3 @@ the platform of your choice. [IBM Cloud](./deployments/ibm.mdx). Deploy HA Teleport on IBM cloud.
- diff --git a/docs/pages/setup/deployments/aws-terraform.mdx b/docs/pages/setup/deployments/aws-terraform.mdx index bf8f51655a4b2..147be3dec01a4 100644 --- a/docs/pages/setup/deployments/aws-terraform.mdx +++ b/docs/pages/setup/deployments/aws-terraform.mdx @@ -7,55 +7,6 @@ h1: Running Teleport Enterprise in High Availability mode on AWS This guide is designed to accompany our [reference Terraform code](https://github.com/gravitational/teleport/tree/master/examples/aws/terraform/ha-autoscale-cluster#terraform-based-provisioning-example-amazon-single-ami) and describe how to manage the resulting Teleport deployment. - - -Our reference Terraform code deploys self-hosted instances of the Teleport Auth -Service and Proxy Service. Since Teleport Cloud manages these services for you, -users interested in Terraform should consult the following guides instead of -this one: - - - - -Read our guide to using Teleport and Terraform - - - - -Read our Terraform provider reference - - - - -You can also view this guide as a user of another Teleport edition: - - - - - - - - - - - - ## Prerequisites Our code requires Terraform 0.12+. You can [download Terraform here](https://www.terraform.io/downloads.html). We will assume that you have @@ -883,5 +834,3 @@ $ ./connect.sh proxy 1 # connect to the node $ ./connect.sh node ``` - - \ No newline at end of file diff --git a/docs/pages/setup/deployments/gcp.mdx b/docs/pages/setup/deployments/gcp.mdx index 57942adf4ccd0..47b46938b37d8 100644 --- a/docs/pages/setup/deployments/gcp.mdx +++ b/docs/pages/setup/deployments/gcp.mdx @@ -12,27 +12,8 @@ high-level introduction to setting up and running Teleport in production. This guide shows you how to deploy the Auth Service and Proxy Service, which Teleport Cloud manages for you. -You can view this guide as a user of another Teleport edition: - - - - - - - - - - We have split this guide into: - [Teleport on GCP FAQ](#teleport-on-gcp-faq) @@ -248,5 +229,3 @@ proxy_service: **4. Add Users** Follow [adding users](../../enterprise/getting-started.mdx#adding-users) or integrate with [Google Workspace](../../enterprise/sso/google-workspace.mdx) to provide SSO access. - - \ No newline at end of file diff --git a/docs/pages/setup/deployments/ibm.mdx b/docs/pages/setup/deployments/ibm.mdx index 4db24b18208bc..22eeb815fc5ac 100644 --- a/docs/pages/setup/deployments/ibm.mdx +++ b/docs/pages/setup/deployments/ibm.mdx @@ -12,27 +12,8 @@ introduction to setting up and running Teleport in production. This guide shows you how to deploy the Auth Service and Proxy Service, which Teleport Cloud manages for you. -You can view this guide as a user of another Teleport edition: - - - - - - - - - - We have split this guide into: - [Teleport on IBM FAQ](#teleport-on-ibm-cloud-faq) @@ -217,4 +198,3 @@ the Teleport Proxy public address. public_addr: proxy.example.com:3080 ``` - \ No newline at end of file diff --git a/docs/pages/setup/guides/joining-nodes-aws-ec2.mdx b/docs/pages/setup/guides/joining-nodes-aws-ec2.mdx index ea657e6c63340..e829ef2cf950e 100644 --- a/docs/pages/setup/guides/joining-nodes-aws-ec2.mdx +++ b/docs/pages/setup/guides/joining-nodes-aws-ec2.mdx @@ -13,27 +13,8 @@ The EC2 join method is not available in Teleport Cloud. Teleport Cloud customers can use the [IAM join method](./joining-nodes-aws-iam.mdx) or [secret tokens](../admin/adding-nodes.mdx). -You can view this guide as a user of another Teleport edition: - - - - - - - - - - The EC2 join method is available in self-hosted versions of Teleport 7.3+. It is available to any Teleport node or Proxy running on an EC2 instance. Only one Teleport node or Proxy per EC2 instance may use the EC2 join method. @@ -302,4 +283,3 @@ spec: aws_role: "arn:aws:iam::333333333333:role/teleport-DescribeInstances-role" ``` - \ No newline at end of file diff --git a/docs/pages/setup/operations/scaling.mdx b/docs/pages/setup/operations/scaling.mdx index e2ccc7b022378..216cbfc8a99c8 100644 --- a/docs/pages/setup/operations/scaling.mdx +++ b/docs/pages/setup/operations/scaling.mdx @@ -11,27 +11,8 @@ deployments of Teleport. For Teleport Cloud customers, the settings in this guide are configured automatically. -You can view this guide as a user of another Teleport edition: - - - - - - - - - - ## Prerequisites - Teleport v(=teleport.version=) Open Source or Enterprise. @@ -76,4 +57,3 @@ $ cat /proc/$(pidof teleport)/limits # Max open files 65536 65536 files ``` - \ No newline at end of file diff --git a/docs/pages/setup/reference/backends.mdx b/docs/pages/setup/reference/backends.mdx index a96820f4fb201..e134270ec3337 100644 --- a/docs/pages/setup/reference/backends.mdx +++ b/docs/pages/setup/reference/backends.mdx @@ -12,28 +12,8 @@ stored data (size, read/write ratio, mutability, etc.). Teleport Cloud manages Auth Service and Proxy Service data for you, so there is no need to configure a backend. - -You can view this guide as a user of another Teleport edition: - - - - - - - - - - | Data type | Description | Supported storage backends | | - | - | - | | core cluster state | Cluster configuration (e.g. users, roles, auth connectors) and identity (e.g. certificate authorities, registered nodes, trusted clusters). | Local directory (SQLite), etcd, AWS DynamoDB, GCP Firestore, self-hosted PostgreSQL/CockroachDB (Preview) | @@ -703,5 +683,3 @@ $ psql -d postgres postgres=# CREATE DATABASE teleport; postgres=# GRANT ALL PRIVILEGES ON DATABASE teleport TO dbuser; ``` - - \ No newline at end of file