Is there some secret sauce for using OCI Helm repo...
# kubernetes
s
Is there some secret sauce for using OCI Helm repos? Per https://hub.docker.com/r/thethingsindustries/lorawan-stack-helm-chart
Copy code
helm install <name> <oci://registry-1.docker.io/thethingsindustries/lorawan-stack-helm-chart>
Below gives
error: failed to pull chart: could not find protocol handler for:
Copy code
ttn-deploy:
  type: kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>
  properties:
    chart: thethingsindustries/lorawan-stack-helm-chart
    version: 0.0.3
    name: lorawan-stack-helm-chart
    namespace: things
    repositoryOpts:
      repo: <http://registry-1.docker.io|registry-1.docker.io>
I've tried setting repo to
<oci://registry-1.docker.io/>
which throws
error: failed to pull chart: looks like "<oci://registry-1.docker.io/>" is not a valid chart repository or cannot be reached: object required
Update- found an open ticket, OCI not yet supported sad panda
m
Hi @straight-arm-50771, helm Release supports OCI.
Copy code
name: kubernetes-yaml
runtime: yaml
description: "Test"

resources:
  minecraft-exporter:
    type: kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>
    properties:
      chart: <oci://ghcr.io/dirien/charts/minecraft-exporter>
      version: 0.11.1
      name: minecraft-exporter
      namespace: default
In my example, I use ghcr.io as registry.
image.png
s
worked like a charm, thank you!