Add E2E test verifying OTEL tracing across Zenko services#2378
Draft
delthas wants to merge 1 commit intodevelopment/2.14from
Draft
Add E2E test verifying OTEL tracing across Zenko services#2378delthas wants to merge 1 commit intodevelopment/2.14from
delthas wants to merge 1 commit intodevelopment/2.14from
Conversation
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
Deploy Jaeger all-in-one in the kind CI cluster, enable OTEL on the Zenko CR with sampling ratio 1.0, and add a @premerge CTST scenario that puts an object then asserts a Jaeger trace exists with spans from both cloudserver and vault. Issue: ZENKO-5258
c362986 to
9a3a251
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not human-reviewed yet. Not asking for reviews at the moment!
Summary
cluster alongside existing dependencies (Keycloak, Prometheus, etc.)
spec.otel(enabled, sampling ratio 1.0) soevery request is traced during CI — this also acts as a smoke test
that OTEL doesn't break existing
@PreMergetests@PreMergeCTST scenario that puts an S3 object and thenpolls the Jaeger query API to assert a trace exists with spans from
both cloudserver and vault
What changed
install-kind-dependencies.shconfigure-e2e-ctst.shkubectl patch zenkowithspec.otel, wait for cloudserver + vault rolloutsetup-e2e-env.shJaegerQueryEndpointin world paramsworld/Zenko.tsJaegerQueryEndpointadded toZenkoWorldParametersfeatures/otel-tracing.feature@PreMergescenariosteps/otel-tracing.tsOTEL.mdWhy
Parent ticket OS-1072
tracks adding OpenTelemetry tracing across the Zenko stack. This PR
adds CI coverage to verify that traces actually propagate end-to-end
(cloudserver → vault) once OTEL is enabled on the CR.
Issue: ZENKO-5258