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.

Sign up for GitHub

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

[v17] docs: update cloud networking on proxy service #48145

Merged
merged 11 commits into from
Nov 4, 2024
Merged

[v17] docs: update cloud networking on proxy service #48145

Changes from 9 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
06c30c5
docs: update cloud networking on proxy service
stevenGravy Oct 11, 2024
7b0b801
docs: update verbiage for networking
stevenGravy Oct 22, 2024
21f3ede
docs: update cloud-hosted public address
stevenGravy Oct 22, 2024
02249c2
docs: update verbiage for app access for networking
stevenGravy Oct 24, 2024
4ca34e9
docs: update verbiage for public address for networks with cloud
stevenGravy Oct 28, 2024
4c23dc5
docs: clarify app configuration
stevenGravy Oct 29, 2024
3dc70d5
docs: update cloud-hosted explanation for public address
stevenGravy Oct 29, 2024
3902731
Update docs/pages/reference/networking.mdx
mmcallister Oct 31, 2024
9ff3acc
Merge branch 'branch/v17' into bot/backport-47506-branch/v17
stevenGravy Nov 1, 2024
d29922b
Update docs/pages/reference/networking.mdx
mmcallister Nov 1, 2024
b1e54a9
Merge branch 'branch/v17' into bot/backport-47506-branch/v17
stevenGravy Nov 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 2 additions & 14 deletions docs/pages/reference/networking.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,21 +36,9 @@
</TabItem>
<TabItem scope={["cloud", "team"]} label="Cloud-Hosted">

All Teleport services (e.g., the Application Service and Database Service) have
an optional `public_addr` property that you can modify in each service's
configuration file. The public address can take an IP or a DNS name. It can also
be a list of values:

```yaml
public_addr: ["service-one.example.com", "service-two.example.com"]
```
On Teleport Enterprise (Cloud) the Teleport agent services always

Check failure on line 39 in docs/pages/reference/networking.mdx

View workflow job for this annotation

GitHub Actions / Lint docs prose style 

[vale] reported by reviewdog 🐶
[messaging.capitalization] Capitalize the names of Teleport services and features (Teleport agent is incorrect). See the Core Concepts page (https://goteleport.com/docs/core-concepts/) for a reference.

Raw Output:
{"message": "[messaging.capitalization] Capitalize the names of Teleport services and features (Teleport agent is incorrect). See the Core Concepts page (https://goteleport.com/docs/core-concepts/) for a reference.", "location": {"path": "docs/pages/reference/networking.mdx", "range": {"start": {"line": 39, "column": 36}}}, "severity": "ERROR"}
mmcallister marked this conversation as resolved.
Show resolved Hide resolved
connect using reverse tunnels so there is no need to set a public address for an agent.

Specifying a public address for a Teleport agent may be useful in the
following use cases:

- You have multiple identical services behind a load balancer.
- You want Teleport to issue an SSH certificate for the service with additional
principals, e.g., host names.
</TabItem>
</Tabs>

Expand Down
Loading