filpano

According to these two: https://github.com/spring-cloud/spring-cloud-config/issues/1856#issuecomment-820528524 https://github.com/spring-cloud/spring-cloud-config/issues/1856#issuecomment-820541005 comments, it seems this is a indeed a supported feature. I'll get a PR to enhance the documentation up within the next few days.

Just a note: https://github.com/spring-cloud/spring-cloud-kubernetes/pull/673 was merged 12 days ago (21.01.2021).

Is there a longer-term solution that does not include setting `security=False`? IMO, that's not a production-grade configuration since it leaves connections to the scheduler and workers susceptible to MITM attacks....

Digging a bit deeper, it seems the change in behaviour occurred between `kafkacat 1.6.0` and `kcat 1.7.0`.

Have you tried `edenhill/kcat:1.7.1`? It includes Avro support. ```bash $ docker run edenhill/kcat:1.7.1 -V kcat - Apache Kafka producer and consumer tool https://github.com/edenhill/kcat Copyright (c) 2014-2021, Magnus Edenhill Version 1.7.1...

> Hi @nick4fake if you could give a hand: > > > changing replication factor to 3 > > Where did you change this? Is this the `default.replication.factor = 3`...

Sorry for the late feedback. I've created an example repository where this problem can be seen: https://github.com/filpano/jpa_exception_demo/tree/main There are tests for both the `JpaRepository` as well as the `EntityManager#createNativeQuery` approach...