-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix kubectl log
commands when they refer to deployment instead of pod
#32912
Conversation
This PR fixes a typo on our automatic updates documentation where the `kubectl log` commands should refer to the deployment since Kubernetes appends random strings to deployment names when building the pod name. Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
``` | ||
|
||
And by consulting its logs: | ||
|
||
```code | ||
$ kubectl logs <your-agent-release>-updater | ||
$ kubectl logs deployment/<your-agent-release>-updater |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it a deployment or a statefulset? Looks like the latter to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updater is a deployment. The agent itself is a statefulset
https://github.com/gravitational/teleport/blob/master/examples/chart/teleport-kube-agent/templates/updater/deployment.yaml
🤖 Vercel preview here: https://docs-hs4lcrv2l-goteleport.vercel.app/docs/ver/14.x |
This PR fixes a typo on our automatic updates documentation where the
kubectl log
commands should refer to the deployment since Kubernetes appends random strings to deployment names when building the pod name.