Daniel Haß

@tchiotludo would love to hear your feedback on this before moving on.

@tchiotludo I get your concern. Actually I don't know enough about Micronaut to comment on the precedence of the different ways of setting the jwt generator secret. I don't know...

@tchiotludo thanks for the feedback and clarifying the precedence of configs in Micronaut. I'm not sure if I get your proposal right but I would not be a huge fan...

@treff7es we ran into the same issue using a on-prem Confluent cluster with mTLS auth active. We found the packaged `ingestion_executor` config in the datahub-actions container in the following path:...

We digged into this further with a little help from @Masterchen09 and the links from the error message above we came up with the following workaround in the `executor.yaml` config:...

Wanted to provide an additional reproduction of this issue. Situation during we faced this issue was reproduced by the following steps: - Rancher v2.6.3 cluster running on k8s v1.21.8 +...

One statement of the maintainer from not too long ago can be found here #388.

@almarklein I could really benefit from a notification if my current record is running for x hours. I played around a little and tried to hack a notification into the...

@hellt thanks for re-opening this as a new issue!

I sure think that the points from my comment above need to be sorted out as they are blocking a proper deployment of DataHub with an external mTLS enabled Kafka...