Troubleshooting datahub errors and schema registry configuration in Kubernetes deployment using Helm charts

all-things-deployment
21

created a PR to fix this. Could someone take a look at this when you have time, please…? :pray:
• <Sign in to GitHub · GitHub enable SPRING_KAFKA_PROPERTIES_AUTO_REGISTER_SCHEMAS by LittleWat · Pull Request #358 · acryldata/datahub-helm>

22

Thank you <@U05MNM3P96U> While waiting to be merged and released, is there a way to change the value of this environment variable through the values.yaml? I want to test this on our dev environement

23

Here is what I ended up doing in my helm releases, it is inspired by the PR.
• pre-reqs values yaml file :

  enabled: true
  cp-schema-registry:
    enabled: true
    kafka:
      bootstrapServers: "datahub-prerequisites-kafka:9092"```
• values.yaml : 
```global:
  kafka:
    bootstrap:
      server: "datahub-prerequisites-kafka:9092"
    schemaregistry:
      type: KAFKA
      url: "<http://datahub-prerequisites-cp-schema-registry:8081/>"

# ADDED
datahubSystemUpdate:
  extraEnvs:
    - name: "KAFKA_PROPERTIES_AUTO_REGISTER_SCHEMAS"
      value: "true"```
24

Sweet, thanks for sharing!

25

> While waiting to be merged and released, is there a way to change the value of this environment variable through the values.yaml? I want to test this on our dev environement
I think there is no way through the values.yaml :man-facepalming: You can patch the environment variable, though. (If the INTERNAL schema registry is unstable, it might be better to use the cp-schema-registry)

26

I see, Got help from a colleague experienced with helm, he came to the same conclusion.

After investigating the chart, we discovered the extraEnvs block as well as the environment use when schema Registry type is KAFKA.

that solution has stabilized our dev deployment of datahub, will trying PROD next week

27

[FYI] My pr got merged: <Sign in to GitHub · GitHub enable SPRING_KAFKA_PROPERTIES_AUTO_REGISTER_SCHEMAS by LittleWat · Pull Request #358 · acryldata/datahub-helm>
so it should work with the latest helm chart. :bow: