Add jaeger helm chart#79
Conversation
|
Do we intend to have zipkin running locally? or can we remove the zipkin tracing stuff if we are going to use jaeger? Also, is there a particular reason we have the ingress created and the api exposed? Is it just to be able to view the routes that are being created? |
|
We should also look at having these things disabled by default when we install the helm chart in the integration tests :P or else our tests are going to take much longer to run 😄 |
| kind: CustomResourceDefinition | ||
| metadata: | ||
| name: tlsoptions.traefik.containo.us | ||
|
|
There was a problem hiding this comment.
This needs the CRD Hook annotations :)
| rewrite continue { | ||
| name regex ([a-z]*)\.([a-z]*)\.traefik\.mesh traefik-{1}-{2}.traefik-mesh.svc.cluster.local | ||
| answer name traefik-([a-z]*)-([a-z]*)\.traefik-mesh\.svc\.cluster\.local {1}.{2}.traefik.mesh | ||
| name regex ([a-z0-9-_]*)\.([a-z0-9-_]*)\.traefik\.mesh traefik-{1}-{2}.traefik-mesh.svc.cluster.local |
There was a problem hiding this comment.
Do you think we need to add capitals to this? I only ask due to being unsure if case-sensitive DNS is an issue...
There was a problem hiding this comment.
Yes I think that we should add capitals.
|
Blocked by traefik/traefik#5007 |
|
traefik/traefik#5007 has been merged. Ready to proceed once the experimental image is built. |
|
Will test tonight or tomorow and report back if wanted :) |
3 participants
Description
This Pr adds jaeger tracing in the project