-
Notifications
You must be signed in to change notification settings - Fork 131
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
Add a helm chart #113
Add a helm chart #113
Conversation
Welcome @krmichel! |
@MrHohn Here is the PR for the helm chart as promised |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @krmichel! I'm not particularly familiar with the helm chart templating, but tried to go over the configuration and RBAC etc. and they looks sane to me.
I have a comment regarding the multi-arch image and will LGTM after that.
/approve
I can create that once this PR is merged. |
You can wait until after the merge. If you do the action to release the chart will fail right after the merge. However, I think you can then create the branch and go into the actions and tell it to rerun them. |
@MrHohn, sorry I think I just accidentally cleared your approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work @krmichel!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krmichel, MrHohn The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@krmichel gh-pages branch is created on https://github.com/kubernetes-sigs/cluster-proportional-autoscaler/tree/gh-pages. |
The "Release Helm Charts" job failed initially as you mentioned. I manually rerun it and it is all good now. Let me know if you see any more issue. |
@MrHohn I forgot that because the github release was already created the workflow doesn't think it needs to do anything for the chart version. I think the options are either we delete the release and the tag so the actions sees that it needs to run or I (or someone) make a PR bumping the chart version to 1.0.1 and merge it to make sure it creates the needed file in the gh-pages branch. |
Hello guys! Sorry for bothering, but is there any update on this workflow?
Thanks in advance! :) |
So I went for the first approach and hit another issue:
Looks like we might need something similar to kubernetes-sigs/aws-ebs-csi-driver#624 as you mentioned. |
@MrHohn This PR has been merged do you want to delete the release and tag and try again? |
@krmichel Thanks for that - I didn't know that config lives in prow :) Re-run the job and it completes successfully this time. |
@VioletCranberry I think it is working now |
Fixes #103
Before this is merged there will need to be a
gh-pages
branch created (probably with nothing but a .gitignore file in it) to house the chart repo's index.yaml. If you need any help let me know and I can provide some git commands to help with that. In the event that thegh-pages
branch is protected here is a PR in another kubernetes-sigs repo that needed to be changed with a reference to a change in test-infrakubernetes-sigs/aws-ebs-csi-driver#624