Add TraceTTL to cassandra schema spec

[moolen]

This adds the CassandraSchemaSpec.traceTTL field to allow the user to specify the TTL for their traces.
The TRACE_TTL env var is picked up by this script which creates the schema: https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/cassandra/schema/create.sh

fixes #1101

[codecov]

Codecov Report

Merging #1111 into master will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1111      +/-   ##
==========================================
+ Coverage   88.00%   88.05%   +0.04%     
==========================================
  Files          86       86              
  Lines        5254     5274      +20     
==========================================
+ Hits         4624     4644      +20     
  Misses        466      466              
  Partials      164      164              

Impacted Files	Coverage Δ
pkg/apis/jaegertracing/v1/jaeger_types.go	100.00% <ø> (ø)
pkg/storage/cassandra_dependencies.go	100.00% <100.00%> (ø)
pkg/config/ca/ca.go	100.00% <0.00%> (ø)
pkg/inject/sidecar.go	94.38% <0.00%> (+0.20%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e7ad3f0...429ad55. Read the comment docs.

[moolen]

The es-otel test seems flaky, it runs fine locally. Can i re-run this check individually without git commit --amend and force-pushing?

[jpkrohling]

LGTM. @kevinearls, is this ES failure known to you? If so, we can merge this as is, or we can try to restart the job via GitHub (which typically will cause everything to randomly fail...). Or, @moolen could try to amend and force-push and see if the test passes :-/

[kevinearls]

@jpkrohling which es failure?

[moolen]

I take that back, i don't think it's flaky: I reproduced the issue locally (i missed exporting the USE_OTEL_COLLECTOR env var before running es tests) and it continuously fails in CI. I'll dig into that.
stacktrace of the pod that runs jaegertracing/spark-dependencies : https://gist.github.com/moolen/091b62d537bab7f01c9f8072ad6d19a2

[jpkrohling]

If you nee any help, let us know!

[jpkrohling]

Sorry, not docker container but container image :)

[jpkrohling]

This is not a blocker, though. Would you prefer me to merge this as is, or would you want to get this change in ?

[moolen]

Oh, what a misunderstanding :D I'll fix that for sure!

[jpkrohling]

Thank you for your contribution!