Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Explain the relation to cloud-on-k8s in README
See original GitHub issueChart version: ./.
Kubernetes version: ./.
Kubernetes provider: E.g. GKE (Google Kubernetes Engine) ./.
Helm Version: ./.
helm get release output
./.
Describe the bug: Both the helm-charts and the cloud-on-k8s project seem to provide ways to deploy an elastic-stack on Kubernetes. It’d be nice if the relationship between the two project would be added to README in the form of one sentence. Usage recommendation for novice and advanced users would be appreciated.
Since there’s a lot of redundancy between the two approaches to use helm and copy-paste snippets from the quickstart guide of cloud-on-k8s it’d be nice to explain why these two approaches are maintained in a very short statement.
Steps to reproduce: Read the REAMDE.
Expected behavior: Being certain that I use the right project/approach to get an elastic stack running on k8s.
Provide logs and/or server output (if relevant): ./.
Any additional context: ./.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
still valid
This issue has been automatically closed because it has not had recent activity since being marked as stale.