Helm chart for kuberex #12
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
mikluko/kuberex#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Map: #1
Question
Write the Helm chart for kuberex in this repo (
chart/) and publish it as an OCI chart next to the image (sarak.sh/mikluko/kuberex), released with the image. Rex and Claude Code are in the image, so the pod is plain:Recreate, one replica), one container runningkuberex run, non-root (999), read-only root filesystem, all capabilities dropped, seccompRuntimeDefault./var/lib/rex, the tailnet settings (TS_HOSTNAME, join-key Secret,TS_CONTROL_URL), ServiceAccount name, a CiliumNetworkPolicy toggle for egress.Resolved when the chart renders and passes
kubeconform -strictandhelm lint, and the release workflow pushes it.Answer
Chart
oci://sarak.sh/mikluko/charts/kuberex(chart/in this repo), released with the image at the same version; 0.4.0 is published (merged in PR 15).Recreate; uid/gid 999,fsGroup999, read-only root, all capabilities dropped, seccompRuntimeDefault;/run/rexand/tmpare emptyDirs.stateVolume: volume source of/var/lib/rex, rendered as given (hostPath,persistentVolumeClaim, ...); emptyDir when empty.tailscale.hostname,tailscale.controlURL,tailscale.authKey.existingSecret/.key(mounted asTS_AUTHKEY_FILE).serviceAccount.create/.name(default: release name) /.automountToken(default false).networkPolicy.enabled: CiliumNetworkPolicy, egress to kube-dns, kube-apiserver andworldonly.nodeSelector,tolerations,affinity,resources,env,podLabels,podAnnotations,imagePullSecrets.charts/and not next to the image: a chart namedkuberexthere would take the image's own reference.helm lint --strictandkubeconform -strict(Cilium CRD schema included) overchart/ci/*.yaml.