https://rancher.com/ logo
Join Slack
Powered by
Can anyone verify that this should work? <https://...
# fleet
w
Can anyone verify that this should work? https://fleet.rancher.io/0.13/ref-fleet-yaml#chart
Copy code
It is possible to download the chart from a Git repository, e.g. by using git@github.com:rancher/fleet-examples//single-cluster/helm. If a secret for the SSH key was defined in the GitRepo via helmSecretName, it will be injected into the chart URL.
c
should probably be git:// - that is not a valid URI as written since it is missing a scheme. maybe try that?
This can refer to any go-getter URL
w
unsupported protocol scheme \"git\""
that does explain the double-slash here: fleet-examples//single (so I'll update that too)
c
the go-getter docs suggest that it should work as-is, given how it does protocol detection
have you tried it as-is?
go-getter calls it a URL but it’s really kinda their own thing
w
I could try this
Copy code
git::<http://github.com/mitchellh/vagrant.git>
c
yes but the example you quoted would do it over ssh given that it’s a user@host:path/to/repo
if you wanted to do it over http then yes you should use a http uri instead of a git+ssh uri
w
I can take a step back. I'm basically just trying to target a helm chart in a private git repo directly by its folder path
c
do you want to use ssh or http? git uses totally different formats for the repo uri depending on how you want to access it
w
i don't have a preference, just whichever fleet can support
c
it will do either, you just need to use the correct uri for what you want. YOU need to decide.
w
the docs aren't terribly explicit there
https would be preferred, the same pattern as the GitRepo
c
I mean, you should know how git works if you want to refer to a repo. The following are equivalent, but use different protocols • 
<https://github.com/rancher/fleet.git>
for https • 
git@github.com:rancher/fleet.git
for ssh
This is just like, how git works though
w
I totally understand, it's just not how fleet is working
I expected my use of 
git@github.com:rancher/fleet.git
to work, it didn't, it gave me that original error message
c
which error
you said you got that when doing git:// which I see from the go-getter docs is not what they want
w
sorry, it was posted in the message after the one where the thread was started
"When I target a repo this way, I am getting the error: 
first path segment in URL cannot contain colon
"
c
what exactly were you using as the chart url
w
git@github.com:krumIO/rancher-catalog-default
c
Yeah that’s not correct. You need to specify the path to a specific chart, not just a repo. In the example 
git@github.com:rancher/fleet-examples//single-cluster/helm
git@github.com:rancher/fleet-examples/
is the repo and 
/single-cluster/helm
is the path to the chart in the repo. You’re only providing the repo.
w
Job Failed. failed: 1/1time="2025-07-30T19:05:18Z" level=fatal msg="failed to process bundle: failed to resolve URL of repo=git@github.com:krumIO/rancher-catalog-default//chart/krum-boot chart=krum-boot version=: parse \"git@github.com:krumIO/rancher-catalog-default//chart/krum-boot/index.yaml\": first path segment in URL cannot contain colon"
maybe it's possible that my ssh-key isn't being picked up correctly. I used https for the GitRepo object, so that secret is at least validated
the error message doesn't indicate that specifically, but it wouldnt surprise me if there isn't a check and throw error prior to that step
c
maybe try the 
git::
prefix? The fleet docs suggest that should work, if it’s actually using go-getter as it says it is
w
that just gives the error: 
unsupported protocol scheme \"git\""
c
hmm. that seems pretty broken. Maybe open an issue in the fleet repo?
you’ve confirmed you’re using the correct version of fleet that these docs are valid for?
https://fleet.rancher.io/0.13/ref-fleet-yaml#helm-chart-download-options also suggests that any go-getter URL should work in the 
chart
field
either the docs are wrong in multiple places or you’re not using fleet 0.13
w
I'm on Rancher 2.11.3 prime, which looks like fleet 0.12.4, so the docs would be here: https://fleet.rancher.io/0.12/ref-fleet-yaml#helm-options
c
probably worth an issue then. If you can provide the full fleet.yaml that you’re using that might be helpful
w
but this section is interesting:
that almost infers that the chart field should be specifying the repo path, and the 
repo
field is just the name of the chart?
I'll try that now shrugg
c
yes. that is what the other section I linked to says as well
are you putting it in the chart field, or the repo field?
both sections say it goes in chart
w
I was putting it in the repo section 🤦
c
oh, why would you do that
Main options
chart
This specifies a custom location for the Helm chart. This can refer to any go-getter URL or OCI registry based Helm chart URL
You’re reading the chart field docs
not the repo field
w
from primarily following the yaml reference
the use of the word 
repo
is particularly confusing there, with a URL as the example
and I definitely know the differences
c
right but you’re providing the path to a specific chart, in the chart field
w
yea I expected 
repo
to be the URL, then the 
chart
to be the subpath
obvious docs being obvious, i still didn't make the connection
c
you can do repo + chart + version if the repo supports indexes, or just point it at a specific chart URL. the helm CLI works the same way
w
look, I know how the mechanisms work at the core there, but they don't always translate to other tools in those ways
so honest mistake on my part to mix that up
jumping around between oci compliant, published or private, direct file reference in git, local paths, I guess I got twisted there
but i definitely appreciate the help
3 Views
Open in Slack
PreviousNext
Powered by