docs: Reduce the use of capitalized trusted clusters and a few other fixes#32432
docs: Reduce the use of capitalized trusted clusters and a few other fixes#32432lsgunn-teleport merged 7 commits intomasterfrom
Conversation
lsgunn-teleport
temporarily deployed
to
vercel
GitHub Actions
Inactive
github-actions
Bot
requested review from
ptgott,
r0mant,
xinding33 and
zmb3
lsgunn-teleport
had a problem deploying
to
vercel
GitHub Actions
Failure
|
🤖 Vercel preview here: https://docs-4ju3r95w5-goteleport.vercel.app/docs/ver/14.x |
| Trusted Clusters. | ||
| ### Trusted clusters | ||
|
|
||
| A **trusted cluster** consists of a **root cluster** and one or more **leaf clusters** |
There was a problem hiding this comment.
Technically "trusted cluster" is singular and doesn't "consist of" multiple clusters.
We often use the term "trusted clusters" to mean "any setup where you have multiple clusters that have some sort of trust relationship between them."
In the singular form though, "trusted cluster" typically refers to a root cluster. For example, if cluster A is a root and cluster B is a leaf, then cluster B has one "trusted cluster" resource pointing at cluster A.
There was a problem hiding this comment.
"trusted cluster" typically refers to a root cluster.
Your explanation makes sense to me in the sense that the leaf trusts the CA of the root. However, I don't think I would say that is the "typical" usage. I've seen it used generically and used to mean the leaf cluster. It seems to be what this paragraph originally said: the "remote cluster" (the leaf) joins "your cluster" (the root).
Treating "Trusted Cluster" and "Trusted Clusters" as proper nouns encourages ambiguity.
I didn't go through and try to make all of the contextual changes. Still, I think it makes a lot more sense to talk about in terms of a trust relationship between a root cluster and a leaf cluster and do away with the generic references to Trusted Clusters or a trusted cluster that sometimes means the root and sometimes means the leaf.
lsgunn-teleport
had a problem deploying
to
vercel
GitHub Actions
Failure
lsgunn-teleport
temporarily deployed
to
vercel
GitHub Actions
Inactive
|
🤖 Vercel preview here: https://docs-j0hu4kz6b-goteleport.vercel.app/docs/ver/14.x |
| <TabItem scope={["cloud","team"]} label="Cloud-Hosted"> | ||
|
|
||
| When multiple Trusted Clusters are present behind the Teleport Proxy Service, the | ||
| When multiple trusted Clusters are present behind the Teleport Proxy Service, the |
There was a problem hiding this comment.
| When multiple trusted Clusters are present behind the Teleport Proxy Service, the | |
| When multiple trusted clusters are present behind the Teleport Proxy Service, the |
public-teleport-github-review-bot
Bot
removed request for
r0mant and
xinding33
|
🤖 Vercel preview here: https://docs-pb9sq4ob8-goteleport.vercel.app/docs/ver/14.x |
|
🤖 Vercel preview here: https://docs-inw2s3at1-goteleport.vercel.app/docs/ver/14.x |
|
@lsgunn-teleport See the table below for backport results.
|
3 participants
No description provided.