https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
m
I can’t seem to find YAML definitions. I’m looking for something like this: https://github.com/traefik/traefik-helm-chart/blob/master/traefik/crds/ingressroute.yaml Actually, I realized I can just do 
kubectl get crd <http://helmcharts.helm.cattle.io|helmcharts.helm.cattle.io> -o yaml
also. So apparently the schema is not strictly defined?:
Copy code
spec:
            x-kubernetes-preserve-unknown-fields: true
          status:
            x-kubernetes-preserve-unknown-fields: true
Would be nice to know a bit more about supported values and their behavior, e.g.:
Copy code
apiVersion: <http://helm.cattle.io/v1|helm.cattle.io/v1>
kind: HelmChart
spec:
  chart: <what are expected values and what behavior do they trigger?>
  set:
    global.systemDefaultRegistry: "" <- what does this do?
  valuesContent: <this is obvious based on existing docs>
c
A few of the newer fields are missing but most of them are documented here: https://rancher.com/docs/k3s/latest/en/helm/#helmchart-field-definitions
🙌 1
Do you want the CRD manifest, or do you want documentation?
The yaml CRD definitions are at the top of both of the yamls in the GH release I linked you to.
m
Basically I’d like to understand the behavior, e.g. can I pass some external chart URL (e.g. of OCI repo containing a chart)
I’d like to set up some own charts doing k3s boot and instead of providing raw tgz files, I’d like to utilice OCI repo
@creamy-pencil-82913 Does it support pulling from same registry as images? I have set up mirroring to private Harbor registry, and during boot all images are pulled correctly. Does that CRD use different pull mechanism? If I don’t specify repo, I’m getting error, but not sure what’s correctly repo URL format and whether authentication mechanism other than what I’ve set to containerd is required.
hm, I guess helm needs to login to the register separately unrelated to containerd
c
The spec just wraps creation of a job pod that runs the helm CLI tool from a shell. It doesn't have any special abilities with regards to 'pulling' charts beyond what helm itself has.
m
Would it make sense to have such feature? I.e., specify the charts to load and have ability to also specify OCI registry credentials..? I can of course just put the chart tarballs to 
/var/lib/rancher/k3s/server/static/charts
to make them accessible for HelmChart, but would be nice to be able to pull directly from registry.
c
The job image currently includes helm 3.8.1, which supports pulling charts from OCI registries. The job image does not currently support authentication (
helm registry login
) though, so you’d be limited to public registries. If we were to add auth support, it would probably be via a Secret that contained the credentials, similar to how pod ImagePullSecret works.
144 Views
Open in Slack
PreviousNext
Powered by