teleport config retrieval from configmap example #39566
Conversation
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
WilliamLoy
added
the
no-changelog
WilliamLoy
changed the title
|
🤖 Vercel preview here: https://docs-65ocmql94-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-5qx5vplmm-goteleport.vercel.app/docs/ver/preview |
Co-authored-by: Zac Bergquist <[email protected]>
|
🤖 Vercel preview here: https://docs-gyfl4luno-goteleport.vercel.app/docs/ver/preview |
| @@ -485,6 +485,9 @@ $ kubectl exec -i my-pod -- tctl status | |||
| # sending local files via stdin | |||
| $ kubectl exec -i my-pod -- tctl create -f < my-local-file.yaml | |||
|
|
|||
| # retrieving the teleport service config file from the configmap | |||
| $ kubectl get configmap teleport-cluster-auth -o jsonpath="{.data['teleport\.yaml']}" | |||
There was a problem hiding this comment.
It looks like this only refers to the Auth Service configmap in the teleport-cluster chart. Do we have a user-friendly way to list all available configmaps first? E.g., kubectl get configmaps in the appropriate namespace? Or we could include similar example commands for the Proxy Service in teleport-cluster and agents in teleport-kube-agent.
There was a problem hiding this comment.
The other examples seemed like they were assuming some knowledge but i'm an advocate for adding more details. @zmb3 do you think this will bloat things too much or should we add them in?
There was a problem hiding this comment.
I think this is good enough to merge. We're just including a few snippets for how to accomplish common tasks in this section, not trying to teach the ins and outs of how to use kubectl.
|
@WilliamLoy See the table below for backport results.
|
This example shows users how to retrieve the teleport.yaml file from distroless pods.