wireapp / wireapp/wire-server-deploy
Question: Injecting values like password and keyspace when installing via helm
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 113
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Basic information
- On-premises: yes
- Cloud-Provider: none
- Installation type: production
- Kubernetes version: 1.22.7(vanilla)
- Helm version: v1.10.0
- Installed with Kubespray: no
- (Helm) Charts version: 5.5.0
- List of installed top-level charts:
How did you install Wire?
Using the process from https://docs.wire.com/how-to/install/helm-prod.html
Using external Cassandra and Minio and vanilla Kubernetes that has not been setup using the wire provided scripts.
Question
When trying to install wire component like wire server in kubernetes using helm, cannot find entries in the provided values.yaml file provided in github repo, for injecting values like cassandra password, minio password, setting custom cassandra keyspace name and setting protocols like http or https for communicating with components like elasticsearch. I am using the values.yaml file from master branch in wire-server-deploy folder for production.
Contributor guide
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 with the production Helm installation guide at docs.wire.com/how-to/install/helm-prod.html and the values.yaml file in the wire-server-deploy repository. Check how external Cassandra and Minio credentials, a custom Cassandra keyspace, and Elasticsearch HTTP or HTTPS settings are represented in the chart. Done means the available configuration and required value injection paths are documented or exposed clearly for the production installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100