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

Tracetest installation with examples on Kubernetes via CLI is incomplete #2143

Closed
danielbdias opened this issue Mar 10, 2023 · 3 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@danielbdias
Copy link
Contributor

Describe the bug

When we run tracetest server install, choose the option Using Kubernetes -> Just learning tracing! Install Tracetest, OpenTelemetry Collector, and the sample app., the PokeshopAPI is installed relying on jaeger, which is not installed.

After the installation, the user can run Tracetest, but without any provision profile installed. When calling our demo APIs we don't have telemetry, because the telemetry config is using a jaeger address, that is not installed on the cluster.

@danielbdias danielbdias added bug Something isn't working triage requires triage labels Mar 10, 2023
@danielbdias danielbdias self-assigned this Mar 15, 2023
@danielbdias danielbdias removed the triage requires triage label Mar 15, 2023
@danielbdias
Copy link
Contributor Author

This problem is not happening anymore on v0.11, closing it.

@danielbdias
Copy link
Contributor Author

This problem is still happening on some versions, I will investigate it again on v0.11.6.

@danielbdias
Copy link
Contributor Author

It happened because we changed the OTLP ports and forgot to update our helm charts. Fixed it on kubeshop/helm-charts#488 and kubeshop/helm-charts#487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant