- Remove the `team` scope from config.json.
- Edit the Edition comparison table to remove the "Team" column.
- Change the Teleport Team getting started guide to a Teleport
Enterprise Cloud getting started guide.
- Remove other Teleport Team mentions from the docs.
The changes in #38161 reorganized pages in the Server Access section of
the docs, but did not add redirects for these pages. This change adds
the missing redirects.
Closes#10583
The local user we show how to create in the `teleport-cluster` guide
only has privileges to access Kubernetes resources, but does not have
administrative access to the cluster (e.g., to manage dynamic
resources).
This change takes the approach of the Linux server guide (the index page
of the docs) and shows how to add a user with the `editor,access` roles
in addition to a role that can access Kubernetes clusters.
* Add a Discovery Service section
Closes#38741
Add a dedicated sidebar section for the Teleport Discovery Service.
Since the Discovery Service is a separate agent service from the SSH
Service, Kubernetes Service, etc., it makes sense to add a dedicated
section for this service. In the future, we can include configuration
guides, architecture guides, etc. in this section.
To create the new section, this change moves existing auto-discovery
guides from other sections of the docs.
* Respond to hugoShaka feedback
- Move the Kubernetes application discovery docs
- Edit the "Kubernetes Access" intro to include a link to Kubernetes
auto-discovery
* Simplify and fix Kubernetes Getting Started guide
Fixes#36026
- **Remove `kubernetes_users` in the example role**. Teleport
impersonates a user with the Teleport user's name if the user has no
`kubernetes_users` values, so don't provide one in this guide.
- **Remove the step to choose manual or guided enrollment**. The rest of
the guide only shows the guided enrollment, making Step 1 redundant.
- **Reorder sections.** Move the step to create RBAC resources first.
This way, we can refer to the Kubernetes RBAC resources we created
earlier when connecting to the cluster.
- **Condense redundant steps re: testing the connection:** There are two
separate steps that test access to the cluster. Condense these
instructions to simplify the guide.
- **Edit the "Set up and test access" section:** Include steps that more
closely resemble the flow of the guide, including the namespace and
groups to include in the "Test Connection" view.
- **Have the user fetch pods in the `teleport-agent` namespace**, since
we created the namespace in the guide and can guarantee the output.
* Add context between instructions
Responds to tigrato feedback
* Fix misspellings
* Add OpenSSH Server access to list of unsupported features for Hardware Key support.
* Update docs/pages/access-controls/guides/hardware-key-support.mdx
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Remove `.drone.yml` and `dronegen` which generates it from the repo,
disabling drone on master. Remove references to drone in docs.
The remaining piplines in `.drone.yml` were the tag build and promote
pipelines which now run on GitHub Actions, the push build pipelines that
are currently of limited value and will be re-done differently with a
little thought, and the `teleport-docker-cron-ecr` pipeline which no
longer works as of v15 due to the removal of the legacy OCI images (the
teleport-labs stuff that the pipeline builds is to be removed shortly
too).
* Adds a `Windows Desktop Service` section to scaling
Also adds a link in the windows desktop reference page, as well
as including the CLI in the reference page bullet list.
* link to the specific hash
* add nav slugs for DB CA migration and rotation guides
* add DB CA guides
* use --phase last in CA rotation guide example commands, so they're less tedious to
edit
* link to the database CA rotation guide for db and db_client CA rotation
* deprecate spec.ca_cert in db reference
* recommend parallel database ca rotation
* explain reconfig post rotation to fix db vuln
* update cspell to ignore -noout
* fix indention in helm code example
localAuth: false must be nested under authentication whereas the example appears it can be at the same indention as enterpriseImage
* Update CHANGELOG.md
* Update TAG version to 1.11.0
* Add a guide for deploying TAG using Helm
* Fix prose lint
* Add auto-generated reference for TAG Helm chart
* Apply suggestions from code review
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Update TAG example role to v7
* Fix link to TAG Helm guide
* Pin TAG Helm chart version
Pins to the same version as TAG itself,
Helm chart and TAG are versioned in lockstep
* Call out the teleport Helm chart more explicitly
* Bump TAG version to 1.13.0
Expecting it to be released by the time these docs go live.
* Replace teleport-cluster parameters with Vars
* Elaborate trust of the TAG CA in Teleport
* Fix the marker style
* Fix the link to teleport-cluster reference
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* docs: updates to cloud tenant data locations
* spelling fix
* lint fixes
* update verbiage on where ent cloud runs
* Team data storage update in comparsion
See #36816
The docs are inconsistent in using "automatic updates" vs. "automatic
upgrades". Prefer the former to be consistent with the
`teleport-ent-updater` script.
- Replace "automatic upgrade" with "automatic update" in docs pages.
- Replace "automatic upgrade" uses in the `teleport-kube-agent` chart
and regenerate the docs.
- Catch uses of "automatic upgrade" in the `consistent-terms` Vale rule
Fix an incorrect sitemap link. The Teleport docs engine generates the
sitemap based on the contents of `docs/pages`. This directory tree
included a file called `docs/pages/server-access/guides/openssh.mdx`,
but the `config.json` for the docs content included a redirect from this
page to `docs/pages/server-access/guides/openssh/openssh.mdx`, meaning
that a page in the sitemap became inaccessible.
This change fixes the `/server-access` section of the docs to resolve
the sitemap issue. To do so, it creates the `server-access/openssh`
directory and moves OpenSSH guides into this directory. It updates
`config.json` and the Server Access menu page accordingly.
This change also adds a missing meta description to the self-hosted
Access Graph guide.
The documentation for the Access Graph has been updated to better reflect its functionalities. It now states that the tool visualizes access to all resources, instead of merely SSH servers, enrolled with your Teleport clusters. It also removes the limitation of only supporting SSH nodes.
Closes#17421
Expand the "Docker" section of the Installation guide. The required
instructions are fairly straightforawrd, so this note is mainly to
assure users that this is possible.
* Set the access request max duration to 14 days.
The max duration for an access request is now 14 days. The default requester
role is now set to allow for this as well.
* Tweak comments, docs.
* Add in Okta requester/Okta resources so that we're not modifying the base requester role.
* Fix init tests, fix okta-resources role name.
* Add user group read to the preset.
* Rename okta-resources to okta-access.
* Use role version 7.
Closes#12660
We have moved all information for documentation contributors to the
README of `github.com/gravitational/docs`. This change removes this
information from the Teleport docs site.
The advantages of this approach are that:
- All information for docs contributors is in one place
- We can free up a navigation sidebar entry, since we no longer need the
"Contribute" link.
* Fix bug in opsgenie plugin mixing up notify-services and schedules
* Update docs for opsgenie plugin to use correct schedules
* Remove accidental change to opsgenie client
* Update opsgenie client tests
Paul Gottschling