Split sensitive and non-sensitive info when deploying on kubernetes using helm

[pantelis-karamolegkos]

I see an example here about how to set a values.yaml file when deploying with helm.

The problem is that values.yaml include both sensitive

e.g.

  akhq:
    security:
      enabled: true
      default-group: no-roles        
      basic-auth:
        - username: changeme
          password: changeme
          groups:
            - admin
        - username: changeme
          password: changeme
          groups:
            - reader

and non-sensitive info.

Is there an example somewhere about how to split this information when deploying using helm?

[tchiotludo]

You can use all these:

akhq/helm/akhq/values.yaml

Lines 35 to 62 in 5c4b3e6

	## Or you can also use configmap for the configuration...
	configuration:
	akhq:
	server:
	access-log:
	enabled: false
	name: org.akhq.log.access
	##... and secret for connection information
	existingSecrets: ""
	# name of the existingSecret
	secrets: {}
	# akhq:
	# connections:
	# my-cluster-plain-text:
	# properties:
	# bootstrap.servers: "kafka:9092"
	# schema-registry:
	# url: "http://schema-registry:8085"
	# type: "confluent"
	# basic-auth-username: basic-auth-user
	# basic-auth-password: basic-auth-pass
	# connect:
	# - name: "my-connect"
	# url: "http://connect:8083"
	# basic-auth-username: basic-auth-user
	# basic-auth-password: basic-auth-pass

mostly configuration & secrets