Kubernetes operator · BatleHub

weebo-batlehub

Drive BatleHub, the package registry proxy-cache, from Kubernetes: its instances today, then its configuration, registries, package governance and maintenance — with GitOps-friendly status.

1 · Install the chart
helm install weebo-batlehub \
  oci://ghcr.io/batleforc/charts/weebo-batlehub \
  --namespace weebo-batlehub --create-namespace \
  --set certManager.issuerRef.name=<issuer>
2 · Connect an instance
apiVersion: batlehub.weebo.io/v1alpha1
kind: BatleHubLocalInstance
metadata:
  name: main
  namespace: team-a
spec:
  external:
    url: https://batlehub.example.com
    adminTokenSecretRef: { name: batlehub-admin, key: token }

Connect instances

A BatleHubLocalInstance points at a BatleHub; the operator checks it answers and that its token carries the admin role.

Connect an instance

Secrets opt in

The operator only reads a token from a Secret labelled for it: nobody can make it send another Secret of the namespace to a URL of their choosing.

Token Secret

On the weebo kit

Same status, Events, metrics, chart and release pipeline as every weebo operator.

Reason codes