Border0 managed Helm charts:
| Chart Name | Description |
|---|---|
| border0-connector | Helm chart to deploy the Border0 Connector |
Add this Helm repository:
helm repo add border0 https://borderzero.github.io/helm-charts
helm repo updateGet an invite code from the Border0 admin portal connectors page, then:
helm install border0-connector border0/border0-connector \
--set config.inviteCode="YOUR_INVITE_CODE_HERE"The connector will exchange the invite code for a token and persist it in a Kubernetes secret automatically.
helm install border0-connector border0/border0-connector \
--set config.token="eyJhbGciOiJIUzI1NiIsIn..."To run a custom container image, set image.override to the full image reference:
helm install border0-connector border0/border0-connector \
--set image.override="ghcr.io/borderzero/border0:dev" \
[ your other flags e.g. invite code OR token, etc... ]Note: The chart uses the Helm release namespace for namespaced resources. Set the namespace with --namespace <namespace> --create-namespace.
If you are using the default image.tag: latest, you may upgrade by restarting the deployment:
kubectl --namespace "YOUR_CUSTOM_NS" rollout restart deployment border0-connectorThis will pull the latest version of the image (assuming image.pullPolicy: Always is set).
If you've set a specific image.tag (e.g., v1.2.0), you need to use helm upgrade to update to a new version:
helm upgrade border0-connector border0/border0-connector \
--namespace "YOUR_CUSTOM_NS" \
--reuse-values \
--set image.tag="v1.2.3"Or if using image.override:
helm upgrade border0-connector border0/border0-connector \
--namespace "YOUR_CUSTOM_NS" \
--reuse-values \
--set image.override="ghcr.io/borderzero/border0:v1.2.3"