We recommend using a namespace other than default to deploy applications in production for reasons like isolation, access management, upgrade management, and overall logical separation of default Kubernetes elements and overall aid in long-term management.

You have to generate secret key and initialization vector:

Outputs example:

Create secret file which will be imported to Kubernetes secret

Parameters

Variable	Description
SECRET_KEY	A key, in the context of symmetric cryptography, is something you keep secret. Anyone who knows your key (or can guess it) can decrypt any data you've encrypted with it (or forge any authentication codes you've calculated with it, etc.).
INITIALIZATION_VECTOR	An IV or initialization vector is, in its broadest sense, just the initial value used to start some iterated process. The term is used in a couple of different contexts and implies different security requirements in each of them.

Create Kubernetes secret from secret file above in custom namespace ennote-onetime

Update all the repositories to ensure helm is aware of the latest versions.

All values are available in helm chart repository

Create the ennote-onetime-values.yml file

Parameters

Variable	Description	Default
namespaceOverride	Namespace where application will be deployed	default
customerName	Name of your client	Default
image.repo	Image repository	registry.ennote.dev/ennote/onetime-c
image.tag	Image tag version (see section Release Notes)	latest
image.pullPolicy	The imagePullPolicy for a container and the tag of the image affect when the kubelet attempts to pull (download) the specified image.	Always
secret.name	Kubernetes secret name	ennote-onetime

Install the latest version of the ennote-onetime-c Helm chart with parameters ennote-onetime-values.yml applied.