Comments (4)
@sw-yx a couple thoughts that might help you make those decisions:
IMO the current chart is not a very good example for people to start. I'm pretty sure everyone running Kubernetes have their own Prometheus, Grafana, etc installed, so having these components in the chart is more bloat than useful, not to mention it's more work for people to make it "production-ready".
Looking at the success of the original Cadence chart, I'd say there is a demand from the community for a chart that they can use out of the box. It was the only publicly available resource for installing Cadence for quite some time, so it was extremely popular.
It also demonstrates that it's possible to create a chart to install a production-ready Cadence/Temporal cluster that works out of the box.
Last, but not least: having an official chart means that people can help each other. If everyone has to cook their own, it's much harder.
I guess the question you need to answer is whether you want to maintain a Helm chart or not. I think it would be beneficial for the community, but I can understand if it's not your primary way to deliver Temporal.
I'd be happy to help steer the Helm chart/Kubernetes operations boat if you decide you want to keep these things around.
from helm-charts.
Are there any plans to work on this in the near future? I'll install a couple temporal instances in the near future and I'd like to get rid of all the "junk" that's currently included in the chart. I'd be willing to provide a PR, but I'd really like to avoid wasting all that work and keep rebasing it for weeks (looking at the number of open PRs; such restructure will potentially conflict with every current PR).
So first question is if you accept PRs for this in the first place and if I send a PR splitting the current chart into two, can you commit to a timely review and merge? I understand if you can't (roadmap, summer, whatever), but (as I mentioned) I won't start working on it if it all goes to waste. Thanks!
from helm-charts.
@mark its a fair question - ownership for this repo has been unclear up til now but we are in the process of handing over to my team. Ultimately we are struggling with clearly communicating what we will or will not accept as we don't want to offer a franken-helm chart that offers all the things - much rather people modify it themselves with some nice examples/pointers from the community. really appreciate your willingness to contribute and we know this area is something we need to work on.
from helm-charts.
hi @sw-yx any updates on this one? Mainly I would be interested in having the Chart repository which as is now I use a forked version on gh-pages but I also value @sagikazarmark feedback and willingness to assist here.
from helm-charts.
Related Issues (20)
- [Feature Request] HTTP API Service exposure
- [Bug] Temporal Helm Deployment Constraints Violations on GKE Autopilot
- [Enhancement] Edit Chart file. Delete redundant value
- [Feature Request] Add ingress for temporal server frontend HOT 3
- [Bug] Create service account after helm install HOT 1
- [Feature Request] Allow `--defaultdb` flag to be passed to schema job
- Invalid archival config HOT 3
- open schema/postgresql/v96/temporal/versioned: no such file or directory HOT 4
- [Feature Request] Allow to skip database creation HOT 2
- [Bug] SQL Schema setup/update does not use TLS HOT 1
- Implementing Dependency-Responsive Liveliness Probes in Frontend Pod
- [Feature Request] sidecar container for schema creation & update jobs HOT 1
- [Bug] ElasticSearch index not created when using existing SQL/Cassandra HOT 4
- [Feature Request] Add TLS support for es-visibility in the helm chart
- Add to chat the ability to mount client certificates for admin tools deployment
- [Feature Request] Document installing from helm repo
- [Feature Request] Support Dual Visibility Setup
- [Feature Request] [Archival] [s3 provider] use IAM role + serviceAccount
- [Bug] self-hosted temporal with AWS RDS (Unable to connect to SQL database) HOT 1
- Visibility config doesn't get rendered if visibility and default store types are different HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from helm-charts.