Agent Deployment

Install the Ennote Agent into your cluster. The agent is available as a signed Helm chart and works on any K8s distribution (EKS, GKE, AKS, OpenShift).

Source Code & Prerequisites

The Ennote Agent is open-source. You can review the source code and Helm chart structure on GitHub: github.com/ennote-io/ennote-agent-chart.

Kubernetes version 1.20 or higher.
Helm version 3.8.0 or higher (Required for OCI registry support).
An active Ennote.io workspace and a generated Agent Bootstrap Token.

Option 1: Bootstrap via CLI (Quickstart)

Pass your short-lived (2-hour) bootstrap token directly via the Helm CLI.

helm install ennote-agent oci://ghcr.io/ennote-io/charts/ennote-agent \
--namespace <YOUR_NAMESPACE> \
--set ennote.auth.token="<YOUR_BOOTSTRAP_TOKEN>"

Option 2: Pre-existing K8s Secret (GitOps)

For GitOps workflows (like ArgoCD or Flux), do not commit your token to version control. Instead, create a K8s secret first:

kubectl create secret generic ennote-auth-secret --from-literal=token="<YOUR_BOOTSTRAP_TOKEN>" -n <YOUR_NAMESPACE>

Then, deploy the chart referencing that secret:

helm install ennote-agent oci://ghcr.io/ennote-io/charts/ennote-agent \
  --namespace <YOUR_NAMESPACE> \
  --set ennote.auth.existingSecretName="ennote-auth-secret" \
  --set ennote.auth.existingSecretKey="token"

Configuration Parameters

ennote.k8s.secretPrefixPrefix added to K8s secrets created by the agent (Default: empty).
ennote.k8s.cleanupOrphansAutomatically delete K8s secrets if removed from the Ennote Cloud (Default: false).
ennote.auth.tokenBootstrap token (Not recommended for GitOps).
ennote.auth.existingSecretNameName of existing K8s secret containing the token.

Need Help?

If you encounter any issues or have questions, don’t hesitate to contact support. Our team is here to assist you with any challenges you might face.