https://github.com/osquery/osquery logo
Join Slack
Powered by
not sure what path its the correct one
# fleet
s
not sure what path its the correct one
z
Let me know if that works
s
Will check - I've also noticed that you are using old 'v' prefix in version which is not the best using helm v2
still getting "invalid chart reference: failed to get chart version for remote reference: no 'fleet' chart with version matching '4.32.0'"
z
@Robert Fairburn Do you have a second to look at this ^ Or @Kathy Satterlee 馃槃
r
Chart version is v5.0.1 with app version v4.32.0 My local I just installed and hit CTRL+C on:
Copy code
% helm list
NAME 	NAMESPACE	REVISION	UPDATED                             	STATUS	CHART       	APP VERSION
fleet	default  	1       	2023-05-25 14:02:42.554451 -0500 CDT	failed	fleet-v5.0.1	v4.32.0
s
I have it in separated helmrepository/helmrelease yamls, can you check if you can find the chart with helm search repo?
let me check also with v5.0.1 in helmrelease
r
Copy code
% helm repo add fleet <https://fleetdm.github.io/fleet/charts> 
"fleet" has been added to your repositories
 % helm search repo
NAME       	CHART VERSION	APP VERSION	DESCRIPTION           
fleet/fleet	v5.0.1       	v4.32.0    	A Helm chart for Fleet
s
maybe this -> fleet/fleet is my problem
i was using only fleet as a chart name
r
If i were to install without a 
helm repo add
, this is the one-liner I'd use:
Copy code
helm upgrade --install fleet fleet \
  --namespace <your_namespace> \
  --repo <https://fleetdm.github.io/fleet/charts> \
  --values values.yaml
s
Ok, I will mess around 馃檪 I have to use repository.yaml and release.yaml to work with current ci/cd pipeline. Problem is that helm does not support / in the cart name so when I will pass this it won't parse properly. I see that there is possible workaround in providing first part "fleet" after repo name and then fleet as a name - let me check if that works 馃槈
Didn't work - problem is that chart has / in the name which is against naming convention of charts I guess
I will still look for workaround 馃檪
r
Let me check something. I think 
fleet/fleet
in that case was 
repo/chart
since I called my repo 
fleet
when I added it.
s
Thats possible
I have this stripped like that: repository.yaml
Copy code
apiVersion: <http://source.toolkit.fluxcd.io/v1beta2|source.toolkit.fluxcd.io/v1beta2>  
kind: HelmRepository  
metadata:  
  name: fleetdm  
  namespace: fleetdm 
spec:  
  url: <https://fleetdm.github.io/fleet/charts>  
  interval: 24h
release.yaml
Copy code
apiVersion: <http://helm.toolkit.fluxcd.io/v2beta1|helm.toolkit.fluxcd.io/v2beta1>  
kind: HelmRelease  
metadata:  
  name: fleet  
  namespace: fleetdm
spec:  
  releaseName: fleet  
  chart:  
    spec:  
      chart: fleet  
      sourceRef:  
        kind: HelmRepository  
        name: fleetdm  
        namespace: fleetdm
      version: "v5.0.1"  
  values:  
    - values.yaml
tried also with version with "fleet-v5.0.1"
r
Is it failing to start to find/install it at all or is it failing the preinstall migrations job? The chart expects all the supporting resources and secrets to be in place in order to run migrations as a preinstall job.
s
It's failing to find the chart - I have tried also to do helm search on the url and it's also failing
not sure if I can search remotely repo
I guess I need to learn a little bit more here 馃槈
r
helm search repo
actually tries to search for a chart name inside of the repos you have installed, so if you installed the repo via 
helm repo add <name> <url>
So what I had to do to get 
helm repo add fleet <https://fleetdm.github.io/fleet/charts>
in order to get the search to work. then you could do a 
helm search repo fleet
and it would look for a chart named fleet Or 
helm search repo fleet --version v5.0.0
if you wanted to search the previous version of the chart.
s
roger that - thank you very much for insights - I will try to get it working
r
I'm not immediately seeing in the yaml for your fluxcd what might be wrong, but I haven't used it with fleet personally.
s
Hi Robert, I managed to run it by helmrelease - now I having some problems during migrations but that's a story for another day I guess 馃檪
7 Views
Open in Slack
PreviousNext
Powered by