NOT WORKING: Jaeger example deployment #79
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.
This does not work. Persistent storage does not work applied via Helm chart and sometimes Kube-stack-prometheus, jaeger-collector and jaeger-query break as well. This is somehow PVC/StorageClass related and happened with cassandra deployment trying to allocate volume.
Things I've tried to make Jaeger persistent storage available:
Badger
No Helm chart support for Badger. Possible CRD deployment using kubectl or kubernetes-alpha-provider for Terraform is available, see: https://github.com/jaegertracing/jaeger-operator/blob/65490e8fdc240b3bf9a25297dfc1627372134791/examples/with-badger-and-volume.yaml
Cassandra persistent storageClass: "azure-disk-retain" or different storageclass as well
Does not bind to said storageClass and create PVC like it should ( see https://github.com/bitnami/charts/tree/master/bitnami/cassandra )
Omitted the storageClass configuration so it uses default provisioner
This works and it creates a new PVC, binds to it but its retain policy's not 'retain' so it deletes itself when pod drops.
Suggestions to continue development:
More info if deciding to go with cassandra deployment:
waits for 750seconds before applying cassandra indexing. If it's too low the database deployment isn't ready by the time
Signed-off-by: Sami Wickström [email protected]