gravitational/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-10-11 22:49:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Helm fixes (#67529)

Browse Source
This commit is contained in:
Steven Martin
2026-06-08 13:56:32 +00:00
committed by GitHub
parent 02a758b23a
commit e72c33426c
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/includes/kubernetes-access/helm/kubernetes-externaladdress.mdx
+2 -2
View File
@@ -4,14 +4,14 @@ Whether an IP or hostname is provided as an external address for the load balanc
<TabItem label="EKS (hostname)">
EKS uses a hostname:
```code
$ kubectl --namespace teleport-cluster get service/teleport -o jsonpath='{.status.loadBalancer.ingress[*].hostname}'
$ kubectl --namespace teleport get service/teleport -o jsonpath='{.status.loadBalancer.ingress[*].hostname}'
# a5f22a02798f541e58c6641c1b158ea3-1989279894.us-east-1.elb.amazonaws.com
```
</TabItem>
<TabItem label="GKE (IP address)">
GKE uses an IP address:
```code
$ kubectl --namespace teleport-cluster get service/teleport -o jsonpath='{.status.loadBalancer.ingress[*].ip}'
$ kubectl --namespace teleport get service/teleport -o jsonpath='{.status.loadBalancer.ingress[*].ip}'
# 35.203.56.38
```
</TabItem>
docs/pages/installation/self-hosted/helm-deployments/disaster-recovery.mdx
+3 -2
View File
@@ -85,7 +85,7 @@ to plan your backup procedure.
If the Teleport Auth Service in your cluster uses AWS Key Management Service for
certificate authority private keys, you must replicate your keys to the new AWS
region before reinstalling the `teleport-cluster` Helm chart. See the [AWS
documentation](https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html")
documentation](https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
for information about using KMS keys in multiple regions.
Note that KMS support is only possible in the `teleport-cluster` Helm chart
@@ -196,6 +196,7 @@ Teleport](./aws.mdx#step-47-configure-tls-certificates-for-teleport).
```code
$ helm install teleport-cluster teleport/teleport-cluster \
--namespace teleport \
--version (=teleport.version=) \
--values teleport-cluster-values.yaml
```
@@ -319,7 +320,7 @@ group-access
Teleport grants access to certificate authority rotations using the
`spec.allow.rules` field - on the `cert_authority` resource - so using role
locking to impose a change freeze will also unintended certificate authority
locking to impose a change freeze will also prevent unintended certificate authority
rotations during the disaster recovery procedure.
Create a lock using a `tctl lock` command. The following example locks the