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.

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

[teleport-update] Version telemetry #50266

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

sclevine
Copy link
Member

This PR detects when the teleport-update binary is used to manage the running version of Teleport and changes the reported upgrader type and version accordingly. This ensures accurate upgrader version reporting for installations of Teleport managed by teleport-update.

This PR also disables window exports, given that they do not update the running installation.

Open question: if we don't disable the old teleport-upgrade package script somehow, it will restart teleport unnecessarily. Should we have teleport-update disable and stop the timer?


The teleport-update binary will be used to enable, disable, and trigger automatic Teleport agent updates. The new auto-updates system manages a local installation of the cluster-specified version of Teleport stored in /opt/teleport.

RFD: #47126
Goal (internal): https://github.com/gravitational/cloud/issues/10289

@sclevine
Copy link
Member Author

@hugoShaka curious if you have thoughts about disabling the teleport-upgrade script's timer to prevent conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant