NatLabRockies / NatLabRockies/openstudio-server-helm
Ability to deploy helm chart on other providers
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 12
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to deploy OpenStudio Server on a custom Kubernetes cluster. While attempting to set that up using the repo here, I realized the way the current app is written, it has logic throughout checking the provider.
The error I'm encountering is related to the creation of the storageclass, but I suspect there are probably other areas where a similar issue would arise were I to fix that one. The storageclass.yaml appears to check for the provider to configure the storage class, but since my cluster's name doesn't match for google, aws, or azure I get an error.
I'm setting up the cluster using Rancher, so I'm not sure how generalizable this issue is outside this approach. I had OpenStudio Server running in Docker Swarm which works fine, but it looks like a Kubernetes Cluster would provide more robustness even if it's a bit more complicated to get running.
I'm not sure if this is a full feature request, or if it's just a matter of altering a few of the helm's configuration files. Working with Kubernetes is pretty new to me, but I'm happy to make a fork to try setting up these changes myself, with some advice on what files would need updates.
Thanks for any help and guidance.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing storageclass.yaml and searching the Helm chart for other provider checks affecting deployment on a custom Kubernetes cluster. Determine the configuration points that assume Google, AWS, or Azure, then verify the chart can deploy without matching those provider names and that the storage class is created successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100