-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
subscribe git channel with Chart.yaml and values.yaml files #159
Comments
@callum-stakater could you please confirm this is the right folder you are targeting to install as Helm chart? https://github.com/stakater-lab/stakater-nordmart-review/tree/main/deploy Based on my understanding of Helm https://helm.sh/docs/topics/charts/ What happen if you don't use OCM appsub to install this helm chart but just use the regular |
Yeah sorry it’s using a leader chart, the Chart.yaml pulls in another generic shared chart via the `dependencies:`
block there, which is also public hosted chart so no auth in the way
To deploy it via helm cli does work BUT you do need to “helm dependency build” first which is maybe what OCM is missing here, I can do some more testing to try validate these assumptions that it is the lack of dependency pull down that is causing what appears to be an empty helmrelease
|
i see
is OCM basically doing a |
@callum-stakater Yes, the OCM app-addon is basically doing a |
It looks like the operator-sdk helm operator "version 2" is going to have this type of support For future note: if we want something similar, we can follow the same design in operator-framework/helm-operator-plugins project. |
If you create a git channel and subscribe to a path that contains a Chart.yaml and values.yaml I would except OCM to be able to deploy the chart similar to how ArgoCD is able too
It seems it is able to determine the Chart.yaml is a helm object and creates a HelmRelease but seems no resources are deployed
Example:
All the content here is publicly available so should be possible to deploy this as is to recreate the issue
Struggling to find any thing relevant in docs or google foo which makes me think I am maybe doing something wrong?
The text was updated successfully, but these errors were encountered: