how to use secrets for the akhq connections

[kalavathiy]

I have created secret for kafka username password and i substited while installing helm but it is not working.Can you suggest some thing.

[tchiotludo]

Maybe you can share something like file configuration inside the pod? We can't help you with a simple it's not working 😜

[kalavathiy]

We have configured the connections under secrets in values.yaml file and we are passing variables for boottrap string and kafkausername and password.While running the helm we are passing the values for the variables like helm install akhq akhq -f values.yaml --set username="Xxxx" but application says no authorisation for kafka in ui after deployed.

[kalavathiy]

Please gimme suggestion what is the best way to configure connections in a secrets.

[marcosschroh]

Any advice on this? How can I set a secret using an env variable? In my case I want to set the value for ssl.keystore.password

[jlcrow]

I would love to see some documentation and understanding of how this is supposed to work. For example I've put my entire connection string in the connection field of the values.yaml and validated that the connection worked. Then uninstalled the chart and created a secret called akhq-secret in my cluster and specified that secret name in the existingSecret field and created a the secret --from-file=application-secrets.yml=myyaml.yaml and had the application just blow up. Since there's next to no documentation on how this is supposed to work, I've pulled the chart and looked at the secret.yaml template and the deployment.yaml template and this is the best assumption I can come up with. How exactly do these pieces of the chart work? existingSecret, secret, kafkaSecret an actual example would help and what's the value of secrets in the chart if the values.

myyaml.yaml

akhq:
  connections:
    crs-staging-cluster:        
      schema-registry:
        url: https://schema-staging.something.com     
      properties:
        bootstrap.servers: "kafka-staging.something.com:443"
        security.protocol: SASL_SSL
        sasl.mechanism: SCRAM-SHA-512
        sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule required username="ui-user" password="pass";

error from pod:

2024-07-01 14:19:47,453 INFO  main         Context$RuntimeConfiguredEnvironment Established active environments: [k8s, cloud, secrets]
2024-07-01 14:19:47,750 ERROR main         io.micronaut.runtime.Micronaut Error starting Micronaut server: Failed to read configuration file: /app/application-secrets.yml
io.micronaut.context.exceptions.ConfigurationException: Failed to read configuration file: /app/application-secrets.yml
	at io.micronaut.context.env.DefaultEnvironment.readPropertiesFromLoader(DefaultEnvironment.java:661)
	at io.micronaut.context.env.DefaultEnvironment.lambda$readPropertySourceListFromFiles$4(DefaultEnvironment.java:518)
	at java.base/java.util.Optional.ifPresent(Unknown Source)
	at io.micronaut.context.env.DefaultEnvironment.readPropertySourceListFromFiles(DefaultEnvironment.java:508)
	at io.micronaut.context.env.DefaultEnvironment.readPropertySources(DefaultEnvironment.java:447)
	at io.micronaut.context.env.DefaultEnvironment.start(DefaultEnvironment.java:277)
	at io.micronaut.context.DefaultApplicationContext$RuntimeConfiguredEnvironment.start(DefaultApplicationContext.java:909)
	at io.micronaut.context.DefaultApplicationContext$RuntimeConfiguredEnvironment.start(DefaultApplicationContext.java:878)
	at io.micronaut.context.DefaultApplicationContext.startEnvironment(DefaultApplicationContext.java:266)
	at io.micronaut.context.DefaultApplicationContext.start(DefaultApplicationContext.java:201)
	at io.micronaut.runtime.Micronaut.start(Micronaut.java:74)
	at org.akhq.App.main(App.java:29)

[jlcrow]

Ok so I did figure out a solution with the helm chart and secrets using the extraEnv array to mount existing password secrets and expose them to the configuration.

configuration:
  akhq:
    server:
      access-log:
        enabled: false
        name: org.akhq.log.access
    connections:
      staging-cluster:        
        schema-registry:
          url: https://schema-staging.something.com     
        properties:
          bootstrap.servers: "kafka-staging.something.com:443"
          security.protocol: SASL_SSL
          sasl.mechanism: SCRAM-SHA-512
          sasl.jaas.config: org.apache.kafka.common.security.scram.ScramLoginModule required username="ui-user" password="${USER_PASSWORD}";

extraEnv: 
  - name: USER_PASSWORD
    valueFrom:
      secretKeyRef:
        name: ui-user
        key: password