-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Helm Chart Deployment Option #290
Comments
Good idea, this may probably be in a dedicated repo, right? I could look into that as well but currently have some time constraints. |
@PacoVK if you need help I can implement a helm chart for this repo. It looks like a really simple deployment from kubernetes point of view so it shouldn't take that much time. |
Sign me up too. I've deployed several Helm charts to k8 using ArgoCD. But I've never made a Helm chart. I'd love to help. |
@tlchaffi if Paco is ok with that then it works for me too. I've developed some golden hełm charts for different companies before but it's going to be faster in a team 😁 |
Thanks, really appreciate that you are willing to take care! Feel free to reach out to share ideas or let us have a discussion here, that anybody can chime in. 👍 |
Sounds ok to me, I'll create a fork today afternoon. I can also add Certificate object with a flag for people using cert-manager. What do you think? |
For the storage layer of Tapir, for example, on Azure, it refers to an Azure storage account / blob account. Do we want the Helm chart to resolve the storage layer? Or should it do like a k8 mounted disk? |
That's on the service account level, you have workload identity using AWS/GCP/whatever annotation ( However there's also ClusterRole and binding to that SA that allows get/watch/list on services, ingresses and nodes. I wonder if those privileges are needed for Tapir to function properly or not. |
@jonasz-lasut concerning the ClusterRole i need to double check again, most of the code for K8s in the example was based on #253 but i guess this is not mandatory for Tapir to function at least in a K8s context. There may be an exception for EKS, but thats open to check. AFAIK AWS also introduced an easier way to handle Pod permissions at reinvent 23 |
@PacoVK ok, for now I've left it behind createClusterRoles flag You can find initial draft of the chart under Chart for now. |
Hi, I've opened a pull request with full helm chart with Helm-docs annotations, generated helm docs and script to generate them locally and a basic pipeline which lints helm chart and checks if the docs were generated if any changes are made to the helm chart. I didn;t iplemented bumping up AppVersion in the helm chart from the build/deploy pipeline of |
I think for the first step this is more than enough to just mention the version bump in the release notes We could automate separately then :) |
@all-contributors please add @jonasz-lasut for example, code |
I've put up a pull request to add @jonasz-lasut! 🎉 |
@all-contributors please add @tlchaffi for review |
I've put up a pull request to add @tlchaffi! 🎉 |
Feature request.
It'd be excellent if we could reference a Helm Chart, from the Helm Chart registry. That way we could use the Terraform Hashicorp / Helm provider to deploy Tapir into a kubernetes service.
The text was updated successfully, but these errors were encountered: