-
Notifications
You must be signed in to change notification settings - Fork 200
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
remove certs and simplify telemetry summarize #1750
remove certs and simplify telemetry summarize #1750
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
/ok to test |
/ok to test |
3 similar comments
/ok to test |
/ok to test |
/ok to test |
9c55600
to
e07b378
Compare
/ok to test |
AJ has just re-enabled the TELEMETRY_ENABLED configuration variable. The next run here should show telemetry being captured. |
/ok to test |
/ok to test |
1 similar comment
/ok to test |
/ok to test |
/ok to test |
/ok to test |
e78a58a
to
b4db92d
Compare
/ok to test |
/ok to test |
e26de8d
to
a939f09
Compare
a939f09
to
1e57c73
Compare
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
/merge |
Description
The goal here is to remove the need for certificates. Any worker that is not in our VPC can talk directly to fluentbit, and fluentbit will be configured with certificates to talk to Tempo. The implementation implication is that we need to run telemetry stuff ONLY on nodes in our VPC. To avoid needing to move all jobs to these nodes, we instead temporarily store telemetry data as artifacts, and in one final job, we process and send telemetry info for all jobs from one job.
Part of rapidsai/shared-workflows#269 and rapidsai/shared-actions#28
Checklist