https://linen.dev logo
Join SlackCommunities
Powered by
When are the helm charts updated? It doesn't appea...
# ask-community-for-troubleshooting
b
When are the helm charts updated? It doesn't appear to happen on merge to master, since there are fixes that went in a week ago that have still not been released.
plus1 1
The helm charts seem to be in constant flux, and are really hindering our ability to deploy. Should we look into another method? Perhaps the kubernetes manifests are more stable?
m
@Brad Clark team is changing helm chart to include them into the main Airbyte release process. I think for a couple of days it will continue unstable. @Kyryl Skobylko do you have more info about it?
k
@Brad Clark We have a few issues with rolling out a propper release workflow for helm charts and right now working on improving it(PR waits for review) Until it gets approved/merged/review, you can use kustomize option that’s available right now. https://docs.airbyte.com/deploying-airbyte/on-kubernetes/ Also FYI: Helm charts are under heavy development rn so things might break from time to time. As for the latest version in helm, it’s https://artifacthub.io/packages/helm/airbyte/airbyte/0.40.12 this right now(since the current release strategy has some flaws in it) Sorry for inconvenience and confusion 😞
b
ah, that doesn't show up after 
helm repo update
so I had no idea
It would really help to use some standard practices, like removing the 
placeholder
in the versions and putting actual version numbers in place so local development and contribution was easier
k
if you need to display all version run: 
helm repo search %repo_name% --versions
b
so is 
0.40.12
newer than 
0.41.2
Copy code
$  helm search repo airbyte-oss --versions
NAME                          	CHART VERSION	APP VERSION  	DESCRIPTION
airbyte-oss/airbyte           	0.41.2       	0.40.8       	Helm chart to deploy airbyte
airbyte-oss/airbyte           	0.41.1       	0.40.9       	Helm chart to deploy airbyte
airbyte-oss/airbyte           	0.41.0       	0.40.7       	Helm chart to deploy airbyte
airbyte-oss/airbyte           	0.40.12      	0.40.10      	Helm chart to deploy airbyte
k
Copy code
It would really help to use some standard practices, like removing the placeholder in the versions and putting actual version numbers in place so local development and contribution was easier
It was already addressed in PR that changes Release workflow, but unfortunately we have some difficulties with getting it through to the master. Main discussion about it is held in this issue
b
Thank you! I'm more than happy to open more PRs to improve the chart. I've done one already and maintain some other public charts as well
octavia thanks 1
k
Copy code
airbyte-oss/airbyte           	0.40.12      	0.40.10      	Helm chart to deploy airbyte
This one is latest. Let me clean up the 0.41.x versions so it’ll make a less confusion(best I can do as for now)
b
I'll start with trying 0.40.12 and see where I land
k
Copy code
Thank you! I'm more than happy to open more PRs to improve the chart. I've done one already and maintain some other public charts as well
Thank you for your interest in improving the helm charts! We appreciate that 🙂
octavia loves
b
I know there have been some issues around helm versioning
Have you considered keeping separate versioning from airbyte releases? That's what we do for PrivateBin (https://github.com/PrivateBin/helm-chart)
We're using https://github.com/helm/chart-releaser to publish them, which is really designed around a stand-alone helm repo, but could probably be implemented in a mono-repo as well.
k
Hmm, we tried but not by using this tool, by simply using a bunch of github actions.
b
k
Good idea though I’ll put it into discussion board
b
this is the action I use for doing the releases. You could change the filter to match tags specifically for the helm chart, to help with versioning
k
I’ll play around with it once I’m back from my vac, but prolly will poke it during the vac itself
b
so then you could cut tags like 
charts-0.40.12
or 
charts-bootloader-0.41.5
, so you could do releases of sub charts or the whole chart independently
🤔 1
Enjoy your time off, thanks for responding
octavia loves 1
k
BTW, did you had any success with 
0.40.12
?
b
i'll try it now. i've been working on another part of the project to get google cloud-sql-proxy working with Airbyte
no, i get an error on the worker pod start about Micronaut
Copy code
2022-10-03 18:21:56 ERROR i.m.r.Micronaut(handleStartupException):338 - Error starting Micronaut server: Failed to inject value for parameter [dslContext] of method [configDatabase] of class: io.airbyte.db.Database
oh let me check my values vs the defaults on v0.40.12
k
Are you using external db configuration?
b
not currently, I was going to test one, but for now it's using the bundled postgres
although i see it spins up both postgres as a stateful set and another db container deployment
k
Oh, I see, yes, let me make a quick PR to fix that
b
the worker pod was pulling the wrong image (0.40.8 vs 0.40.10) so that could have been related, trying again
k
I’ll fix the deployment of the db, since there’s still dependency being used from bitnami repo, but I switched to deploying on my own using just the deployment + pvc
b
what is kept in that db? it seems like a statefulset would be preferable if we are attaching a PVC
but if it's temp data maybe it doesn't matter if it persists...
FYI fixing the worker tag made it come up cleanly
k
afair, user data, configuration, connector images, etc. Everything needed for airbyte to work
Made a changes, will merge them now: https://github.com/airbytehq/airbyte/pull/17516
new ver available under 
0.40.13
b
let me check it out
👍 1
it deploys successfully using minio or gcp storage and the bundled postgres
7 Views
Open in Slack
PreviousNext
Powered by