system-upgrade-controller
system-upgrade-controller copied to clipboard
rancher
introduce helm chart
Sorry the build fails, but this has nothing todo with my changes. I'm not able to fix it. It seems to be a docker issue
Is there any way you can consume the CRDs from the build artifacts, instead of maintaining a static copy in the chart dir?
@brandond: I think it is a good idea. In addition I would like to package the helm during the build. But I'm not familiar with the build process, Could you please tell me how to integrate a helm package step after the usual build where the crd.yaml is created ? Addionally i would relocate it to a crd subfolder according to https://helm.sh/docs/chart_best_practices/custom_resource_definitions/. So please can you tell me how I can change and test the built process ?
I tried bringing up something related here https://github.com/rancher/system-upgrade-controller/issues/172#issuecomment-1123708559
@hurzelpurzel Recent kustomization issues involving the latest tag broke our project, we need this helm chart.
I'm using parts of this helm chart from the PR already to create plans. An official helm chart would be awesome and highly appreciated.
Recently synced my forked repo. Is there anymore that I can do ? Or what is blocking the merge ?
They are not using the cluster admin role anymore, check the latest release 0.13.4
Unfortunately even if this was merged, I don't see any workflow to publish the Helm chart anywhere.
Unfortunately even if this was merged, I don't see any workflow to publish the Helm chart anywhere.
I could look into that
I suggested a helm release action here https://github.com/hurzelpurzel/system-upgrade-controller/pull/1/files But it requires some additional setup by the owners. From the documentation:
Pre-requisites One of these confuguration A GitHub repo containing a single chart in root directory (Chart.yaml) A directory with your Helm charts (default is a folder named /charts, if you want to maintain your charts in a different directory, you must include a settings.charts_dir input in the plugin settings). GitHub branch called gh-pages to store the published charts. In your repo, go to Settings/Pages. Change the Source Branch to gh-pages. Create a .drone.yml file in your root directory. Pipelines examples are available below. For more information, reference the Drone CI Help Documentation for Pipeline Overview
Will try To-Do as suggested
simonfelding @.***> schrieb am Mi., 3. Apr. 2024, 10:28:
I suggested a helm release action here https://github.com/hurzelpurzel/system-upgrade-controller/pull/1/files But it requires some additional setup by the owners. From the documentation https://github.com/otwld/drone-chart-releaser-github-pages:
Pre-requisites One of these confuguration A GitHub repo containing a single chart in root directory (Chart.yaml) A directory with your Helm charts (default is a folder named /charts, if you want to maintain your charts in a different directory, you must include a settings.charts_dir input in the plugin settings). GitHub branch called gh-pages to store the published charts. In your repo, go to Settings/Pages. Change the Source Branch to gh-pages. Create a .drone.yml file in your root directory. Pipelines examples https://github.com/otwld/drone-chart-releaser-github-pages#example-pipeline are available below. For more information, reference the Drone CI Help Documentation for Pipeline Overview https://docs.drone.io/pipeline/overview/
— Reply to this email directly, view it on GitHub https://github.com/rancher/system-upgrade-controller/pull/248#issuecomment-2033901652, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADACKDTNHJMT6ZCJOIQ5JE3Y3O4UDAVCNFSM6AAAAAAZ5VNRGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTHEYDCNRVGI . You are receiving this because you were mentioned.Message ID: @.***>