Skip to content
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

Publish Helm chart on releases #277

Closed
yorugac opened this issue Aug 22, 2023 · 10 comments
Closed

Publish Helm chart on releases #277

yorugac opened this issue Aug 22, 2023 · 10 comments
Assignees
Labels
enhancement New feature or request PLZ
Milestone

Comments

@yorugac
Copy link
Collaborator

yorugac commented Aug 22, 2023

Feature Description

There should be a CI workflow on k6-operator releases publishing Helm chart to the repository.

Suggested Solution (optional)

It appears that all (?) Grafana Helm charts are published here:
https://grafana.github.io/helm-charts/

These can likely be used as code references:

Already existing or connected issues / PRs (optional)

Depends on:

@yorugac yorugac added enhancement New feature or request PLZ labels Aug 22, 2023
@MohanedSaad
Copy link

MohanedSaad commented Sep 22, 2023

Any update on this? is there a way to do the deployment using helm before the k6 operator helm chart is published to be alongside the rest of the helm charts in https://grafana.github.io/helm-charts

@yorugac yorugac self-assigned this Sep 29, 2023
@mladenrtl
Copy link

I have the same question. I am waiting this to be released to helm-charts repository, so I can use it as dependency in our GitOps project, like:

dependencies:
  - name: k6-operator
    version: 1.0.0
    repository: https://grafana.github.io/helm-charts
    alias: k6-operator

I tried to use this but I am getting error:
helm dependency build failed exit status 1: Error: k6-operator chart not found in repo https://grafana.github.io/helm-charts

@mabre69uk
Copy link

until the helm chart will not be release in the grafana repository, will not be usable...can we have an idea of when this will be completed? thanks a lot

@mladenrtl
Copy link

What I do currently, I copy the chart directory to our GitOps repo and use it like that. It works fine, but it's not the convenient way, especially if there are some changes to the chart.

@yorugac
Copy link
Collaborator Author

yorugac commented Oct 6, 2023

Hello 👋
Just to be clear, this issue is not closed yet. So no, our Helm is not published anywhere at the moment. It's an active WIP though.
I'll update here when it's done 👍

@mladenrtl
Copy link

@yorugac Thank you for your reply. Please let me know if you need any help with it, I would like to contribute

@yorugac
Copy link
Collaborator Author

yorugac commented Oct 9, 2023

@mladenrtl, thanks for the offer! I've already had to tinker with the Chart last week: it seems there are some requirements in how folders must be organized to make all the CI Helm tooling work 😕

It is in the branch but putting it as PR here so it's more visible:
#303

I think the only thing left there is getting the correct auth token which is a fully internal process and WIP; but I'm not 100% certain some other caveat won't appear. We'll see!

@mladenrtl
Copy link

@yorugac Thank you very much for the update. I will track this issue, and I hope it will be fixed soon.

@yorugac yorugac added this to the 0.12 milestone Oct 19, 2023
@yorugac
Copy link
Collaborator Author

yorugac commented Oct 20, 2023

A small but happy update 🙂 The epic with Github authentication to helm-charts is finally looking close to the finish line.The 1st version of Helm chart was published yesterday + bump to 0.0.11 today and can now be installed with these commands:

helm repo add grafana https://grafana.github.io/helm-charts
helm install k6-operator grafana/k6-operator

@yorugac
Copy link
Collaborator Author

yorugac commented Oct 20, 2023

Related PR: grafana/helm-charts#2728

Regardless of what happens with this PR to helm-charts, I believe this issue can be considered done: right now, Helm release will be triggered on any change to Chart.yaml in main branch.

This implies that updates of Helm will require manual bumps of versions in Chart.yaml at the moment. It'd be good to somehow automate that in the future as well since releases in k6-operator are becoming too cumbersome will all these manual steps; but for now I consider it sufficient.

@yorugac yorugac closed this as completed Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request PLZ
Projects
None yet
Development

No branches or pull requests

4 participants