gravitational/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-10-12 02:15:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Make internal changelog links relative (#31211)

Browse Source 
Fixes #16050

- Replace absolute `https://gravitational.com` and
  `https://goteleport.com` docs links with relative paths to MDX files,
  allowing the docs linter to check them.
- In one case, a "Documentation" H4 section listed documentation changes
  that were part of a Teleport release. This is the only release note
  that contains documentation changes, so I have removed it to be
  consistent with the rest of the changelog.
This commit is contained in:
Paul Gottschling
2023-08-31 17:25:41 +00:00
committed by GitHub
parent 9de46583d3
commit fdeca03bd8
1 changed files with 27 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+27 -23
View File
@@ -2748,7 +2748,8 @@ auth_service:
#### Upgrade Notes
Please follow our [standard upgrade procedure](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport).
Please follow our [standard upgrade
procedure](docs/pages/management/operations/upgrading.mdx).
## 4.3.9
@@ -2866,15 +2867,10 @@ Teleport 4.3 introduces four new plugins that work out of the box with [Approval
* Fixed `tsh` and `gpg-agent` integration. [#3169](https://github.com/gravitational/teleport/issues/3169)
* Fixed Vulnerabilities in Teleport Docker Image [https://quay.io/repository/gravitational/teleport?tab=tags](https://quay.io/repository/gravitational/teleport?tab=tags)
#### Documentation
* [Moved SSO under Enterprise Section](https://gravitational.com/teleport/docs/enterprise/sso/ssh_sso/)
* [Documented Teleport Plugins](./docs/pages/access-controls/access-request-plugins/index.mdx)
* [Documented Kubernetes Role Mapping](https://gravitational.com/teleport/docs/kubernetes_ssh/#kubernetes-groups-and-users)
#### Upgrade Notes
Always follow the [recommended upgrade procedure](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport?utm_source=github&utm_medium=changelog&utm_campaign=4_3) to upgrade to this version.
Always follow the [recommended upgrade
procedure](./docs/pages/management/operations/upgrading.mdx) to upgrade to this version.
##### New Signing Algorithm
@@ -2885,7 +2881,8 @@ teleport:
ca_signature_algo: "rsa-sha2-512"
```
Rotate the cluster CA, following [these docs](https://gravitational.com/teleport/docs/admin-guide/#certificate-rotation?utm_source=github&utm_medium=changelog&utm_campaign=4_3).
Rotate the cluster CA, following [these
docs](docs/pages/management/operations/ca-rotation.mdx).
##### Web UI
@@ -2904,13 +2901,19 @@ can limit access by changing the options on the new `event` resource.
##### Kubernetes Permissions
The minimum set of Kubernetes permissions that need to be granted to Teleport proxies has been updated. If you use the Kubernetes integration, please make sure that the ClusterRole used by the proxy has [sufficient permissions](https://gravitational.com/teleport/docs/kubernetes_ssh#impersonation).
The minimum set of Kubernetes permissions that need to be granted to Teleport
proxies has been updated. If you use the Kubernetes integration, please make
sure that the ClusterRole used by the proxy has [sufficient
permissions](./docs/pages/kubernetes-access/manage-access/rbac.mdx).
##### Path prefix for etcd
The [etcd backend](https://gravitational.com/teleport/docs/admin-guide/#using-etcd) now correctly uses the “prefix” config value when storing data. Upgrading from 4.2 to 4.3 will migrate the data as needed at startup. Make sure you follow our Teleport [upgrade guidance](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport).
The [etcd backend](docs/pages/reference/backends.mdx#etcd) now correctly uses
the “prefix” config value when storing data. Upgrading from 4.2 to 4.3 will
migrate the data as needed at startup. Make sure you follow our Teleport
[upgrade guidance](docs/pages/management/operations/upgrading.mdx).
**Note: If you use an etcd backend with a non-default prefix and need to downgrade from 4.3 to 4.2, you should [backup Teleport data and restore it](https://gravitational.com/teleport/docs/admin-guide/#backing-up-teleport) into the downgraded cluster.**
**Note: If you use an etcd backend with a non-default prefix and need to downgrade from 4.3 to 4.2, you should [backup Teleport data and restore it](docs/pages/management/operations/backup-restore.mdx) into the downgraded cluster.**
## 4.2.12
@@ -3287,7 +3290,7 @@ The lists of improvements and bug fixes above mention only the significant chang
### Upgrading
Teleport 4.0 is backwards compatible with Teleport 3.2 and later. [Follow the recommended upgrade procedure to upgrade to this version.](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport)
Teleport 4.0 is backwards compatible with Teleport 3.2 and later. [Follow the recommended upgrade procedure to upgrade to this version.](docs/pages/management/operations/upgrading.mdx)
Note that due to substantial changes between Teleport 3.2 and 4.0, we recommend creating a backup of the backend datastore (DynamoDB, etcd, or dir) before upgrading a cluster to Teleport 4.0 to allow downgrades.
@@ -3529,9 +3532,6 @@ usability and performance improvements listed below.
if `kubectl exec` command was interactive.
* Unified (AKA "single pane of glass") RBAC for both SSH and Kubernetes permissions.
For more information about Kubernetes support, take a look at
the [Kubernetes and SSH Integration Guide](https://gravitational.com/teleport/docs/kubernetes_ssh/)
#### Improvements
* Teleport administrators can now fine-tune the enabled ciphersuites [#1999](https://github.com/gravitational/teleport/issues/1999)
@@ -3557,8 +3557,9 @@ on Github for more.
#### Upgrading to 3.0
Follow the [recommended upgrade procedure](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport)
to upgrade to this version.
Follow the [recommended upgrade
procedure](docs/pages/management/operations/upgrading.mdx) to upgrade to this
version.
**WARNING:** if you are using Teleport with the etcd back-end, make sure your
`etcd` version is 3.3 or newer prior to upgrading to Teleport 3.0.
@@ -3662,7 +3663,9 @@ As always, this release contains several bug fixes. The full list can be seen [h
#### Upgrading
Follow the [recommended upgrade procedure](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport) to upgrade to this version.
Follow the [recommended upgrade
procedure](docs/pages/management/operations/upgrading.mdx) to upgrade to this
version.
## 2.6.9
@@ -3790,8 +3793,9 @@ You can see the full list of 2.6.0 changes [here](https://github.com/gravitation
#### Upgrading
Follow the [recommended upgrade procedure](https://gravitational.com/teleport/docs/admin-guide/#upgrading-teleport)
to upgrade to this version.
Follow the [recommended upgrade
procedure](docs/pages/management/operations/upgrading.mdx) to upgrade to this
version.
## 2.5.7
@@ -3876,8 +3880,8 @@ release, which includes:
management, load balancers, etc.
* The Teleport daemon now implements built-in connection draining which allows
zero-downtime upgrades.
[See documentation](https://gravitational.com/teleport/docs/admin-guide/#graceful-restarts).
zero-downtime upgrades. [See
documentation](docs/pages/management/admin/upgrading-the-teleport-binary.mdx).
* Dynamic join tokens for new nodes can now be explicitly set via `tctl node add --token`.
This allows Teleport admins to use an external mechanism for generating