Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edit the Machine ID getting started guide #12868

Merged
merged 2 commits into from
Jun 21, 2022

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented May 24, 2022

Fixes #11806

  • Add more scope-specific information to the Prerequisites section
  • Add the tctl.mdx partial to make it clearer for each scope how to
    connect to the cluster to run tctl commands.
  • Add the Cloud tenant address to the "tbot start" example command for
    Cloud users.

@github-actions github-actions bot requested review from r0mant, xinding33 and zmb3 May 24, 2022 15:01
@ptgott ptgott force-pushed the paul.gottschling/11806-machine-id-cloud branch from 9db0af4 to 39440cd Compare May 24, 2022 15:02
@@ -4,24 +4,25 @@ description: Getting started with Teleport Machine ID
---

In this getting started guide, you will use Machine ID to create a bot user for
a machine and use that identity to connect to said machine.
a machine, then use that identity to connect to the machine.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is technically inaccurate.

The machine you are connecting to is a "host". The identity machine ID is issuing is for a [bot] "user" to connect to said host.

In other words, the identity you create and the machine you connect to are separate. This wording makes them sound the same.

2. Create a bot user
3. Start Machine ID
4. Use certificates issued by Machine ID to connect to a remote machine
1. Download and install Teleport (=teleport.version=) on the host that will run
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we say tbot instead of "Teleport" here?

@@ -157,8 +161,27 @@ the foreground to better understand how it works.
--ca-pin=sha256:1111111111111111111111111111111111111111111111111111111111111111 \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we have some sort of variable we can use for tokens and CA pins in the docs?

@ptgott ptgott force-pushed the paul.gottschling/11806-machine-id-cloud branch from 39440cd to 8180cf5 Compare June 1, 2022 18:59
@ptgott ptgott requested a review from zmb3 June 1, 2022 18:59
@ptgott ptgott force-pushed the paul.gottschling/11806-machine-id-cloud branch from 8180cf5 to 7167577 Compare June 7, 2022 18:02
@ptgott ptgott force-pushed the paul.gottschling/11806-machine-id-cloud branch from 7167577 to ee92be0 Compare June 17, 2022 19:48
@ptgott ptgott enabled auto-merge (squash) June 21, 2022 15:11
ptgott added 2 commits June 21, 2022 11:14
Fixes #11806

- Add more scope-specific information to the Prerequisites section
- Add the tctl.mdx partial to make it clearer for each scope how to
  connect to the cluster to run tctl commands.
- Add the Cloud tenant address to the "tbot start" example command for
  Cloud users.
@ptgott ptgott force-pushed the paul.gottschling/11806-machine-id-cloud branch from ee92be0 to 636cdc5 Compare June 21, 2022 15:14
@ptgott ptgott merged commit d7ca931 into master Jun 21, 2022
@github-actions
Copy link

@ptgott See the table below for backport results.

Branch Result
branch/v10 Create PR
branch/v9 Create PR

@ptgott ptgott deleted the paul.gottschling/11806-machine-id-cloud branch November 3, 2022 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cloud, proxy connection instructions for Machine ID getting started
3 participants